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/loctex_g5.hpp

@@ -0,0 +1,26 @@
+#ifndef LOCTEX_G5_HPP_BVRKEPHW
+#define LOCTEX_G5_HPP_BVRKEPHW
+
+#include <vanetza/geonet/dcc_mco_field.hpp>
+#include <vanetza/geonet/timestamp.hpp>
+
+namespace vanetza
+{
+namespace geonet
+{
+
+/**
+ * Media-dependent extension to the Location Table Entry (LocTE) for ITS-G5
+ */
+struct LocTEX_G5
+{
+    Timestamp local_update; /*< TST_G5: last update time (local time stamp) */
+    Timestamp source_update; /*< TST_SO_PV_G5: SO PV timestamp from SHB header */
+    DccMcoField dcc_mco;
+};
+
+} // namespace geonet
+} // namespace vanetza
+
+#endif /* LOCTEX_G5_HPP_BVRKEPHW */
+