Description

Add a codegen check as part of CI on every PR. Uses the same approach we use in Gloo.

Context

This should prevent master's generated files from falling out of sync with the source files.

[X] I included a concise, user-facing changelog (for details, see https://github.com/solo-io/go-utils/tree/master/changelogutils) which references the issue that is resolved.
[X] If I updated APIs (our protos) or helm values, I ran make install-deps generated-code from tools/wasme/cli to ensure there will be no code diff
[X] I followed guidelines laid out in the Gloo contribution guide
[X] I opened a draft PR or added the work in progress label if my PR is not ready for review
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] I have added tests that prove my fix is effective or that my feature works