Do include the generated checks in make generated_files

Now that they aren't public headers any longer, there's no reason to have a
different mechanism.

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>

docs/architecture/config-check-framework.md

@@ -124,7 +124,7 @@ The generated checks consist of two parts:
 
 The checks are generated by `scripts/generate_config_checks.py` in each project. Each project contains a description of what do check. A Python module in the framework contains code to transform this description into the C header files.
 
-At the time of writing, the output of the generator is checked into each project. `test_generate_config_checks.py` checks that these files are up-to-date (see “[Up-to-date test](#up-to-date-test)”).
+The generation happens before build time as part of `make generated_files` or similar.
 
 ## Validation
 
@@ -137,7 +137,3 @@ The config check tests include some basic unit tests around the code generation,
 ### Checks for forbidden configurations
 
 The config check tests can validate that certain configurations are forbidden. This includes configurations that are forbidden by [manually written checks](#manually-written-checks).
-
-### Up-to-date test
-
-A test case `test_up_to_date` checks that the generated files are up-to-date, by performing the generation and comparing it with the current files.