Keep vanetza-idf in obu-firmware, so a plain clone builds the firmware

obu-firmware builds against the vanetza-idf C-ITS library, which until now
came from the colleague's microbu-esp32c5 tree beside the repository and was
not tracked here, so a clone of this repository could not build the firmware
it ships. The library alone is now part of obu-firmware, as
obu-firmware/external/vanetza-idf: their external/vanetza-idf at commit
cf4b99f, unchanged (9775 files; see its PROVENANCE.md). CMake takes it from
there by default; -DVANETZA_IDF_DIR still points the build elsewhere.

The rest of the colleague's tree (their own VAM firmware, PKI tooling,
station-link Python tools, the V2X2MAP bridge) stays out of this repository
and gitignored; nothing is pushed to their repository. NOTES.md, docs/06,
TODO.md and the pcap verifier's usage line point at the new location.

obu-firmware/external/vanetza-idf/vanetza/geonet/pdu_variant.hpp

@@ -0,0 +1,27 @@
+#ifndef PDU_VARIANT_HPP_AAEVKD5M
+#define PDU_VARIANT_HPP_AAEVKD5M
+
+#include <vanetza/geonet/extended_pdu.hpp>
+#include <vanetza/geonet/beacon_header.hpp>
+#include <vanetza/geonet/gbc_header.hpp>
+#include <vanetza/geonet/shb_header.hpp>
+#include <vanetza/geonet/tsb_header.hpp>
+#include <boost/variant.hpp>
+
+namespace vanetza
+{
+namespace geonet
+{
+
+typedef ExtendedPdu<ShbHeader> ShbPdu;
+typedef ExtendedPdu<TsbHeader> TsbPdu;
+typedef ExtendedPdu<BeaconHeader> BeaconPdu;
+typedef ExtendedPdu<GeoBroadcastHeader> GbcPdu;
+
+typedef boost::variant<BeaconPdu, GbcPdu, ShbPdu> PduVariant;
+
+} // namespace geonet
+} // namespace vanetza
+
+#endif /* PDU_VARIANT_HPP_AAEVKD5M */
+