Turn off 4.13 ci cron + resolve red builds

[emteknetnz]

CMS 4.13 is now in the "Security fix only" phase. The need for keeping the builds green there has been considerably reduced.

Acceptance criteria

• PR to turn off the ci cron for 4.13 builds - see dispatch-ci
• Resolve any outstanding broken builds on 4.13
• Update security release process to manually re-run ci on 4.13 builds that may be affected by high impact patch on the day or release
• Update security fix section in regular release process

PRs

• ENH Disable dispatch for branches on previous major gha-dispatch-ci#14
• FIX Rebuild bundle silverstripe-admin#1739
• DEP Bump minimum queuedjobs version silverstripe-staticpublishqueue#186
• MNT Add .nvmrc silverstripe-gridfield-bulk-editing-tools#282
• FIX Remove broken code to copy diff files to artifacts gha-run-tests#28
• ENH Rebuild bundle silverstripe-admin#1744
• FIX Skip following steps if no dispatch should happen gha-dispatch-ci#16

[GuySartorelli]

PRs merged, reassigning to Steve 'cause Rhino doesn't look happy still

[GuySartorelli]

PRs merged. Reassigning to Steve to check if Rhino is happy.

[GuySartorelli]

Reopening - The CMS 4 CI is still being dispatched. See https://github.com/silverstripe/silverstripe-blog/actions/runs/9281371462/job/25537243483 as an example

It does output the message to say it's skipping it

Workflow is configured to not dispatch workflow for branches on previous major. Exiting.

But then it still continues processing anyway

branch is 3.12

[emteknetnz]

Assigning back to Guy to confirm all is working correctly

[GuySartorelli]

I'll green-ify the remaining 4.13 CI builds once we can see that the cron has stopped running. That will require #267 to be resolved.

[GuySartorelli]

That was merged - now need to wait for the weekend to see if cron runs.

[GuySartorelli]

Crons now skipping CMS 4 as expected. I'll tidy up the remaining CI failures.