Boilerplate - Branch audit

[chris-bateman]

An audit of the cmfive boilerplate branches that can be closed, merged or marked as WIP.
Steps to be taken for the branches to be closed off.

1. Close/merge the PR
2. Delete the Branch - (Yes, they can be restored in a PR. Branches with no PR can also be restored with some Git magic, but it is best to open a PR to review the differences in the branch anyway.)

These branches are already merged. Do you think they can be deleted?

• Fix: tests on nav level bootstrap #76
• Feature: work to codeception5 #66
• Fix: master merge back #64
• Feature/outboard test config for7.4 #63
• fix: Corrected isnull is_null typo #59

These branches have closed PRs. Do you think they can be deleted?

• Consistent playwright runs #86
• Fix: Dev: PHP version hints for CI/CD into Composer #58

These branches are older than two years and have no PR. Can they be reviewed? (Legacy branches excluded)

• https://github.com/2pisoftware/cmfive-boilerplate/tree/fix/PHP8.1_CI_test
• https://github.com/2pisoftware/cmfive-boilerplate/tree/feature/PHP8.1Support
• https://github.com/2pisoftware/cmfive-boilerplate/tree/composer

[DerekCrannaford]

@chris-bateman : I have clicked a few on the assumption of 'tick' = deletion_OK

[chris-bateman]

@chris-bateman : I have clicked a few on the assumption of 'tick' = deletion_OK

Thanks I have deleted the branches on the PRs