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/dcc/channel_probe_processor.hpp

@@ -0,0 +1,32 @@
+#ifndef CHANNEL_PROBE_PROCESSOR_HPP_QBFTHSVC
+#define CHANNEL_PROBE_PROCESSOR_HPP_QBFTHSVC
+
+#include <vanetza/dcc/channel_load.hpp>
+
+namespace vanetza
+{
+namespace dcc
+{
+
+/**
+ * Access point for radio layers to propagate their local channel load measurements
+ */
+class ChannelProbeProcessor
+{
+public:
+    /**
+     * Indicate a new channel load measurement
+     * \see TS 102 686 V1.1.1 Annex A.1.2 for definition of "channel load"
+     *
+     * \param cl locally measured channel load
+     */
+    virtual void indicate(ChannelLoad cl) = 0;
+
+    virtual ~ChannelProbeProcessor() = default;
+};
+
+} // namespace dcc
+} // namespace vanetza
+
+#endif /* CHANNEL_PROBE_PROCESSOR_HPP_QBFTHSVC */
+