Keep the colleague's microbu-esp32c5 tree in this repository

obu-firmware builds against vanetza-idf from microbu-esp32c5/external, but
that tree was gitignored, so a clone of this repository could not build the
firmware it ships. It is now committed here as ordinary files in its own
folder, microbu-esp32c5/: the colleague's commit cf4b99f plus the V2X2MAP
bridge's signature verification (--trust) used on the bench. Nothing is
fetched from or pushed to the colleague's repository; this repository and
its remotes carry everything. The folder's own .gitignore keeps build output,
downloaded components and private key material out, as it did there; the
committed file set is identical to that repository's tracked files.

The ESP32-C5 is still flashed from obu-firmware/, which only takes
vanetza-idf from microbu-esp32c5/, so the two stay separate folders.
FLASHING.md says how to take a newer version of the colleague's tree (copy
it over the folder, rebuild, test, commit).

microbu-esp32c5/external/vanetza-idf/vanetza/btp/data_interface.hpp

@@ -0,0 +1,33 @@
+#ifndef DATA_INTERFACE_HPP_HKI9B5SC
+#define DATA_INTERFACE_HPP_HKI9B5SC
+
+#include <vanetza/btp/data_indication.hpp>
+#include <vanetza/btp/data_request.hpp>
+#include <vanetza/common/byte_order.hpp>
+#include <vanetza/net/packet.hpp>
+#include <memory>
+
+namespace vanetza
+{
+namespace btp
+{
+
+class IndicationInterface
+{
+public:
+    virtual void indicate(const DataIndication&, std::unique_ptr<UpPacket>) = 0;
+    virtual ~IndicationInterface() {};
+};
+
+class RequestInterface
+{
+public:
+    virtual void request(const DataRequestB&, std::unique_ptr<DownPacket>) = 0;
+    virtual ~RequestInterface() {};
+};
+
+} // namespace btp
+} // namespace vanetza
+
+#endif /* DATA_INTERFACE_HPP_HKI9B5SC */
+