refactor(ci/github): run weaver tests on schedule, re-use workflows

[jenniferlianne]

Primary change:

Creates a central workflow to run all 13 weaver test workflows from either a
push, a pull request, a github command, or a schedule.

Passes a 'run_all' boolean to sub-workflows to specify if all tests should be run, not
just those with changes.

Secondary changes:

• update concurrency groups to allow triggering from central workflow
• remove ability to run the 13 workflows individually to declutter ci menu

Notes:

• For example workflow output see here: https://github.com/jenniferlianne/cacti/actions/runs/10062422329 (jobs are displayed as a tree on the left).
• A number of weaver tests are commented out with an 'if false' these were left unchanged.

Depends on #3446

Pull Request Requirements

• Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• [x ] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• [ x] Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

[sandeepnRES]

LGTM, just one optional change if you want to, i.e. rename Test Weaver to Weaver_CI , just like Cactus_CI just to be consistent in naming.
But this is optional just aesthetic, I don't have much issue with current one also.

[petermetz]

@jenniferlianne Agreed, the actionlint looks bugged out. Could you please try to upgrade the actionlint version to the current latest instead of whatever we are using at the moment? I'm hoping that this bug was discovered and fixed a while back!

Also plus one for the rename that @sandeepnRES mentioned above.

[sandeepnRES]

I've removed all weaver checks from required ones from branch protection rules (an exception for this PR as it is refactoring the CI itself), as it was blocking the PR to be merged.
@jenniferlianne please investigate about ActionLint as @petermetz suggested, and once the PR is merged please ping me I'll add new CI checks as required in branch protection rules.

[jenniferlianne]

@petermetz I have updated the ActionLint version to the latest, but it still fails. The linter might be a getting stuck on a permissions issue between repos. (Settings->General->Actions Permissions). Mine is set to run all.

[petermetz]

@jenniferlianne Now I remember! We didn't have time to fix all the linter errors in certain yaml files at the introduction of the ActionLint job and there was no documented way to ignore them so the ActionLint job deletes a list of the yaml files that we wanted to ignore as a workaround. I've just pushed a potential fix, but let's see if it actually works.

[petermetz]

@jenniferlianne I've put the fix here: #3446 once that gets merged to main and this one rebased onto main then the ActionLint job will start passing on this PR as well.

[github-actions]

This PR/issue depends on:

• ci(actionlint): exclude files with very large number of linter errors #3446
  By Dependent Issues (🤖). Happy coding!