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

@@ -0,0 +1,30 @@
+#ifndef DUTY_CYCLE_PERMIT_HPP_9QUTPOPH
+#define DUTY_CYCLE_PERMIT_HPP_9QUTPOPH
+
+#include <vanetza/common/unit_interval.hpp>
+
+namespace vanetza
+{
+namespace dcc
+{
+
+/**
+ * Interface for controlling channel usage by duty cycle limits
+ */
+class DutyCyclePermit
+{
+public:
+    /**
+     * Get allowed channel occupancy for local station in current time window
+     * \return permitted duty cycle
+     */
+    virtual UnitInterval permitted_duty_cycle() const  = 0;
+
+    virtual ~DutyCyclePermit() = default;
+};
+
+} // namespace dcc
+} // namespace vanetza
+
+#endif /* DUTY_CYCLE_PERMIT_HPP_9QUTPOPH */
+