Manually ensure all module have merge-up.yml and dispatch-ci.yml

[emteknetnz]

Module standardiser is being run on all supported repos in this issue https://github.com/silverstripe/.github/issues/242

However, because the default branch is incorrect on some supported modules that are not on the silverstripe account, they will only get their CMS 5 branches updated but not the default branch where the github actions are run

Recommend that you write a script that goes though all the supported modules, and then make a github api call to determine to default branch, then read contents of the default branch to see if the 2x workflow files exist, and then manually create PRs to add them to the default branches

Script used

• https://github.com/emteknetnz/workflow-checker

Notes

• PRs are copied the merge-up.yml + dispatch.yml from the CMS 5 branch to the default branch
• CI is likely to fail on all PRs because the default branches are out of date

PRs

• https://github.com/bringyourownideas/silverstripe-maintenance/pull/224
• https://github.com/bringyourownideas/silverstripe-composer-update-checker/pull/88
• https://github.com/colymba/GridFieldBulkEditingTools/pull/285
• https://github.com/symbiote/silverstripe-advancedworkflow/pull/533
• https://github.com/symbiote/silverstripe-gridfieldextensions/pull/395
• https://github.com/symbiote/silverstripe-multivaluefield/pull/110
• https://github.com/symbiote/silverstripe-queuedjobs/pull/430

[GuySartorelli]

Looks like the only items missed by this are recipes (which we explicitly DO NOT want to have mergeups, so that's good) and things that aren't supported for CMS 5... which is a grey area so I'll leave those be.

[GuySartorelli]

PRs merged. I've run merge-ups, which mostly failed due to conflicts but there's a separate card open to handle that.