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/geonet/repetition_dispatcher.hpp

@@ -0,0 +1,34 @@
+#ifndef REPETITION_DISPATCHER_HPP_GO4BAEVL
+#define REPETITION_DISPATCHER_HPP_GO4BAEVL
+
+#include <vanetza/geonet/router.hpp>
+#include <boost/variant/static_visitor.hpp>
+
+namespace vanetza
+{
+namespace geonet
+{
+
+class RepetitionDispatcher : public boost::static_visitor<void>
+{
+public:
+    RepetitionDispatcher(Router& _router, std::unique_ptr<DownPacket> _payload)
+        : router(_router), payload(std::move(_payload))
+    {}
+
+    template<class REQUEST>
+    void operator()(const REQUEST& request)
+    {
+        router.request(request, std::move(payload));
+    }
+
+private:
+    Router& router;
+    std::unique_ptr<DownPacket> payload;
+};
+
+} // namespace geonet
+} // namespace vanetza
+
+#endif /* REPETITION_DISPATCHER_HPP_GO4BAEVL */
+