@aardappel Could you please review this?

A couple of notes:

• The bazel flatc generation options for tests differ from the cmake flatc gen options. It is outside the scope of this PR, but might make sense to reconcile them both?
• How is the tests/native_type_test_generated.h file generated? Is the purpose of this file to visualize codegen? I added this file to the generate_code script for safe measure. However this file seems to interfere with the CMake build since it prefers this committed file over the codegen from CMake. Is that the intended workflow?

• I am not too familiar with Bazel but yes it probably should.
• Yes, part of the purpose of this project is to generate code, so we need the generated code as part of the repo to be able to see changes to it as part of a diff, as opposed to the common wisdom that generated files should not be in the repo.

Please see the errors in CI, it is actually checking for differences between the python script and CMake which you are violating :)

@aardappel Gotcha! I removed --gen-compare option from the native_type_test to (hopefully) fix the CI errors.

Thanks :)