create example vehicle type build configs for fmu-v2 and fmu-v5

[dagar]

This PR adds vehicle specific builds for px4_fmu-v2 and px4_fmu-v5. These serve as examples for how to easily create specialized builds and ensures we don't introduce dependencies cross module dependencies preventing it.

[dagar]

Revisit after #10964

[LorenzMeier]

We also need to consolidate startup scripts, which will contribute to the major saving - is this easily feasible? Otherwise, an example of a single product might make sense. What I'm concerned about is to make sure we are showing that we can work with XY amount of flash, where XY is preferably < 500KB for a multicopter.

[dagar]

Yes I've been thinking about that as well. I want to get the airframes and mixers sorted into groups and add simple broad dependencies for inclusion. The core RC scripts will be vehicle and board agnostic.

We can also make it easy to have board specific airframes and mixers for things like the crazyflie, aero, bebop, etc. Little things like this will help keep things small and understandable.

[hamishwillee]

Sounds cool, but can we make sure we document all this as soon as it goes in????

My concern is stuff like #10960 (comment) that just magically appears.

[dagar]

TODO: MC + UAVCAN

[dagar]

Rebased.