remove std::vector usage

[dagar]

In several of the distance sensor drivers usage of std::vector has slipped in. This needs to be fixed because std::vector either needs exceptions (PX4 isn't built with c++ exceptions) or a custom allocator. Additionally we need to get the system (toolchain) c++ include path out of the NuttX build to prevent the messy mix of NuttX cxx (https://github.com/PX4/NuttX/tree/px4_firmware_nuttx-7.22%2B/include/cxx) and libstdc++ from the arm-none-eabi-gcc toolchain. @davids5 I believe this is the real reason we're carrying the cstdint fix (PX4/NuttX@198f877).

TODO:

1. remove std::vector usage from these drivers
   • hc_sr04 (https://github.com/PX4/Firmware/blob/8ae3f5009549707eca936cf82becf165f74f1abc/src/drivers/distance_sensor/hc_sr04/hc_sr04.cpp#L126)
   • mb12xx (https://github.com/PX4/Firmware/blob/8ae3f5009549707eca936cf82becf165f74f1abc/src/drivers/distance_sensor/mb12xx/mb12xx.cpp#L134-L136)
   • srf02 (https://github.com/PX4/Firmware/blob/8ae3f5009549707eca936cf82becf165f74f1abc/src/drivers/distance_sensor/srf02/srf02.cpp#L134-L136)
2. Update PX4 usage of all cxx includes not provided by NuttX cxx (cfloat, cinttypes, etc)
3. Start using -nostdinc++ to prevent future mistakes.
4. Reevaluate using LLVM libc++ (long term)

[dagar]

I believe all of the existing usage is to allow each of these drivers to handle multiple sensors. I would propose dropping all of this and extending the module (/driver) itself to run multiple instances. https://github.com/PX4/Firmware/blob/8ae3f5009549707eca936cf82becf165f74f1abc/src/drivers/distance_sensor/srf02/srf02.cpp#L608-L610