move RTPS to dedicated px4fmu-v{3,4,4pro,5}, posix, sdflight builds

[dagar]

RTPS and micro-cdr now only included and required in the following builds

- nuttx_px4fmu-v3_rtps
- nuttx_px4fmu-v4_rtps
- nuttx_px4fmu-v4pro_rtps
- nuttx_px4fmu-v5_rtps

- posix_sitl_rtps

- posix_eagle_rtps
- posix_excelsior_rtps

[davids5]

@dagar - This looks good. Is the CI failure real?

[dagar]

No, that's been failing intermittently.

[bkueng]

This looks good

[bkueng]

Can we move the set of topics to common/rtps? Will be easier to manage.

[dagar]

That sounds fine to me, but I don't think we know how this is actually intended to be used.

[bkueng]

Is the plan to add this to CI? If so, we'll need to check the overhead of building all targets.

[dagar]

Yes, this is for CI.

[dagar]

Apologies for continuing to change this, but what do you think about everything living within modules/micrortps_bridge? micro-CDR, generation, topic lists, etc

Little things like this will help as we work towards large restructuring for modularity (#8127, #8139).

See updated push.

[mcharleb]

Looks good. I'd still like to be able to use the generated agent code without having to sync and build PX4 to get it.

[dagar]

We could have Firmware output a library (with a cmake build system) that's automatically pushed to another github repo. That generated library could be versioned to match Firmware.

[dagar]

Merging now to get it added to semaphoreci. I suspect this will go through a few more iterations once we figure out what to do with the generated agent code and the directory structure refactor.