[No QA] Make schema validations async

[roryabraham]

Details

This is just a minor way to speed up PR checks.

Fixed Issues

$ n/a

Tests

1. Run npm i
2. Run npm run gh-actions-validate. Verify that the script runs successfully.
3. Remove a required key from an action metadata file.
4. Run npm run gh-actions-validate. Verify that the script catches the error, reports it successfully, and exits with a non-zero status code.
5. Restore the action metadata file.
6. Remove a required key from a workflow file.
7. Run npm tun gh-actions-validate. Verify that the script catches the error, reports it successfully, and exists with a non-zero status code.

[aldo-expensify]

Cool update, it runs much faster, but I think there is something to correct.

The exit code is wrong sometimes... if you only remove the "on" and "name" of cla.yml, you can see it detects the invalid file, but the exit code is 0. If you do this same change in main, the exit code is 1.

If I mess up even more the file, like removing the jobs key without removing the descendants, then I get an exit code 1

[roryabraham]

Thanks for testing

[roryabraham]

This is updated now, seems to work as expected

[aldo-expensify]

I think this is what fixed the bug, right?

[roryabraham]

Yeah. When you have an if statement that in-and-of-itself is a command and so it changes the value of $?.

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[roryabraham]

This is working well

[OSBotify]

🚀 Deployed to staging by @aldo-expensify in version: 1.1.83-1 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

[OSBotify]

🚀 Deployed to production by @chiragsalian in version: 1.1.84-13 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅