Add auto patch release functionality to gha- repos

[emteknetnz]

gha-* repos should have auto patch release functionality after PRs to minor branches are merged.

The patch release functionality is at the tail end of CI. gha-* repos don't use the CI like other modules do.

Option A

• move the checkgovernance and gaugerelease steps out of ghi-ci and into a new action that can be shared
• This is probably overkill since we don't really care about things like not tagging for DOC commits or symbiote modules
• Also if we push an old minor we'll gha-auto-tag will mistakenly make this the v1 tag

Option B

• Just make a new release every time something is pushed to a minor branch on gha-* and make sure it's restricted it to the silverstripe account
• This is much simpler and seems better
• Makes sense to have a new cutdown CI (gha-action-ci) for gha-* modules that simply runs phpunit if it's installed and then does a patch release on push event at the tail end of it

Recommend we go with option B here.

Example runs

** Example run of new gha-action-ci running phpunit + making a patch release:**

• https://github.com/emteknetnz/gha-generate-matrix/actions/runs/5817539137

** Example of ci.yml using shared gha-gauge-release action:**

• https://github.com/emteknetnz/silverstripe-config/actions/runs/5826871653

PRs

• NEW Create gha-gauge-release gha-gauge-release#1
• NEW Create action-ci gha-action-ci#1
• ENH Use gha-gauge-release gha-ci#79
• NEW Add action-ci module-standardiser#6
• FIX Update action-ci naming module-standardiser#11
• MNT Run module-standardiser gha-ci#81
• MNT Run module-standardiser gha-run-tests#15
• MNT Run module-standardiser gha-generate-matrix#61
• MNT Run module-standardiser gha-auto-tag#7
• MNT Run module-standardiser gha-pull-request#6
• MNT Run module-standardiser gha-tag-release#16
• MNT Run module-standardiser gha-update-js#16
• MNT Run module-standardiser gha-keepalive#8
• MNT Run module-standardiser gha-dispatch-ci#6
• MNT Run module-standardiser gha-issue#4
• MNT Run module-standardiser gha-merge-up#10
• MNT Run module-standardiser gha-action-ci#2
• MNT Run module-standardiser gha-gauge-release#2

[GuySartorelli]

I recommend option A, which is more flexible and reduces doubled-up-code. Surely we want to use the same logic in gaugerelease for GHA as well?

[emteknetnz]

Maybe a combo? - I kind of put "create a new ci for action gha-action-ci" in option B which seems like it's something we want since it simply make rolling this out to all the gha-* repos easier since there's no code duplication, otherwise we'd need to copy paste the patchrelease step on all the repos

The gaugerelease step makes sense to put into its own action to share since it has some good functionality e.g. ensure it's on the latest commit on a branch before tagging

The checkgovernance step probably not at this stage? for gha-* we only care if it's on the silverstripe account whereas checkgovernance was designed for modules on symbiote account etc.

[GuySartorelli]

PRs merged and tagged.
Reassigning to @emteknetnz to apply the new gha-action-ci to relevant repositories.

[GuySartorelli]

All PRs merged.