[No QA] Schema Validation for Github Actions

[roryabraham]

cc'ing @Dal-Papa - maybe this will be useful for other repos too!

Details

Creates a script which validates the Github Actions and Workflows using the schemas provided by https://json.schemastore.org

• Github Action Schema
• Github Workflow Schema

These schema seem to be pretty actively maintained by the community here.

Uses a YAML validator called ajv, which also seems to be actively maintained.

Fixed Issues

Fixes (partial) https://github.com/Expensify/Expensify/issues/156436

Tests

1. Commit an incorrect value in a Github Action metadata file
2. Push the change, and the validation should fail.
3. Revert any changes in any yaml metadata files. Commit an invalid key in a Github Action metadata file.
4. Push the change, and the validation should fail.
5. Revert any changes in any yaml metadata files. Commit an incorrect value in a Github Workflow metadata file.
6. Push the change, and the validation should fail.
7. Revert any changes in any yaml metadata files. Commit an invalid key in a Github Workflow metadata file.
8. Push the change, and the validation should fail.
9. Revert any changes in any yaml metadata files.
10. Push your changes again (resetting any metadata files except the one intentionally changed by this PR), and the validation should pass.

Tested On

• Github only

[roryabraham]

Note that what this does not do is format linting of yaml files for things like indentation, brackets, etc...

[Dal-Papa]

I'm sure it's for consistency with the rest but why did we decide to proxy all our shell scripts with NPM actions ?

[roryabraham]

It's so you can run them from any directory in the project and they will still work the same. Like it I were to do cd .github && ./scripts/validateActionsAndWorkflows.sh, then the script would fail because it tries to run cd ./.github and that would fail. But if you run it as an npm script then it's always running from the project root.

[Dal-Papa]

Hmm, there are other ways to ensure that in Bash without requiring npm. In this case, this we already use it that's probably fine but we shouldn't rely on it otherwise IMO.
E.g. DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )"

[AndrewGable]

Can you test? Or is this internal QA?

[roryabraham]

Yeah, I can do some more testing in this PR pre-merge. But then I don't think any QA will be necessary because the PR is the environment in which this check is meant to run.

[roryabraham]

Test commit	workflow
e45001f	https://github.com/Expensify/Expensify.cash/runs/2250100875?check_suite_focus=true
b67183c	https://github.com/Expensify/Expensify.cash/runs/2250160817?check_suite_focus=true
286085e	https://github.com/Expensify/Expensify.cash/runs/2250181199?check_suite_focus=true
9e33976	https://github.com/Expensify/Expensify.cash/runs/2250189561?check_suite_focus=true

[pecanoro]

All yours @Dal-Papa and @AndrewGable

[roryabraham]

No changes since @Dal-Papa's last approval, only temporary changes for testing. So going to self-merge this one.