[no-Jira] Run yarn gql:w alongside the Next.js dev server

[canac]

Description

• Keep GraphQL generated files in sync with the source files by committing generated files.
• Add a custom script to delete stale generated files that were left when a .graphql file was moved, renamed, or deleted. These stale files can cause TS errors and were a significant source of confusion.
• Add a GitHub Action that will check that the generated files are up-to-date.
• Speed up yarn gql by not running prettier on the generated files.
• The files in src/graphql/ are not committed because their contents may differ depending on whether yarn gql was pointed at the staging or the production API server.
• Remove post-checkout git hook because it is no longer needed.

Checklist:

• I have given my PR a title with the format "MPDX-(JIRA#) (summary sentence max 80 chars)"
• I have applied the appropriate labels. (Add the label "On Staging" to get the branch automatically merged into staging.)
• I have requested a review from another person on the project

[github-actions]

Bundle sizes [mpdx-react]

Compared against dde4508

No significant changes found

[canac]

@dr-bizz Sorry for another large PR. The vast majority of the files are yarn packages and generated files, which you should be able to ignore. But let me know if you want me to try to split it up more before you review.

[dr-bizz]

Thank you for doing this. Your changes will make it easier for devs to switch between local branches.

I have left a few comments on how you can split up the changes more to ensure there is only one change per commit.
Can you also split this PR into two? One for updating graphql-codegen and the related files, and the other for .generated files and other commits. Having two separate PRs will ensure each PR is focused on one Conceptual change per PR.

[canac]

@dr-bizz I broke the work up into 2 PRs (see #928) and a lot of separate commits. Let me know if that's what you had in mind.

[dr-bizz]

Great work on this. I left a few comments.

[dr-bizz]

Everything looks good so I'm approving this.

Please can you add the package script I mentioned and add some text to the ReadMe explaining why you need to run gql before pushing.

[canac]

I switched to a different approach of running yarn gql:w in parallel when you start the Next.js dev server. It should address all of the pain points of outdated generated files without needing to commit the generated files.

[canac]

I rewrote the bash delete stale files script in node so that it is more readable, maintainable, and robust. Specifically, it will handle filenames containing spaces correctly now.