Migrate emteknetnz gha actions

[emteknetnz]

Create new repos on silverstripe account with emtpy readme only, then fork repos to emteknetnz, and create PRs with copy pasted contents from gha versions so they can all be peer reviewed

I'm thinking we should retain the gha- prefix instead of the github-actions- prefix, and also split the exsiting 'workflow_call' style github-actions-ci-ci repo to a pair of actions to be consistent:

• gha-ci
• gha-update-js (ditch the -deps suffix since it also does a build)

ACs

• gha-run-tests
• gha-pull-request
• gha-tag-release
• gha-auto-tag
• gha-generate-matrix
• gha-ci
• gha-update-js
• gha-keepalive
• Update readme instructions for each so it's clear how to use them
• Add auto-tag action to each workflow in each action
• Update actions/workflows to use silverstripe @v1 versions
• Tag release 1.0.0 of each module
• Validate that errors systematically failed the build
• Validate that pass string input variables and pull request title though env variables
• Validate that Pin third party actions to specific shas works

PRs

• NEW Create action gha-auto-tag#1
• NEW Create action gha-generate-matrix#1
• NEW Create action gha-run-tests#1
• NEW Create workflow gha-ci#1
• NEW Create action gha-pull-request#1
• NEW Create action gha-tag-release#1
• NEW Create action gha-update-js#1
• NEW Create action gha-keepalive#1

The following will be handled with silverstripe/gha-ci#4:

• MNT Rename test class to conform with standard naming convention silverstripe-assets#496
• MNT Rename test class to conform with standard naming convention silverstripe-framework#10353
• MNT Rename test class to conform with standard naming convention (v3) silverstripe-graphql#472
• MNT Rename test class to conform with standard naming convention (v4) silverstripe-graphql#473

[GuySartorelli]

@emteknetnz Can you please add a meaningful description to each of the gha repositories? It will make it a lot easier to know at a glance what each repo is for.

[emteknetnz]

Descriptions are in the readme.md of each pull-request

[GuySartorelli]

6 months down the track, nobody will want to open each repo to remember, for example, the distinction between gha-auto-tag and gha-tag-release or what the purpose of gha-pull-request is. It's good practice to have a meaningful description for repositories.

[emteknetnz]

Oh, are you referring to text field in the actual github repo i.e.

?

[GuySartorelli]

Yes, that's the one. Sorry, I should have been more explicit.

[emteknetnz]

Have added descriptions on the silverstripe account repos

[GuySartorelli]

@emteknetnz PRs merged. I think the next step is for you to create a 1 branch for each repo and create a PR that swaps from using @main to @v1