BSP CI Sanitization

[ztnel]

Description

Now that the autogenerated BSP code is in lockstep with the project .ioc file, we should have a CI check to ensure that generation of the BSP via CubeMX does not deviate from what was committed. In a perfect world, the autogenerated code should not be committed to source control however, due to the complexity in running CubeMX headless and integrating it directly into the CMake build process, it is easier to source control the autogenerated code directly.

The most effective solution would be to implement a custom github action which hosts a headless CubeMX runtime and use it mode to run the following steps:

1. Copy the BSP files into a tmp folder
2. Run the code gen on the tmp folder
3. Run a file diff comparing tmp to BSP
4. Fail on any diffs, otherwise pass