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/security/v2/tests/check_signature.hpp

@@ -0,0 +1,30 @@
+#ifndef CHECK_SIGNATURE_HPP_7RESWTUO
+#define CHECK_SIGNATURE_HPP_7RESWTUO
+
+#include <vanetza/security/v2/signature.hpp>
+
+namespace vanetza
+{
+namespace security
+{
+
+void check(const EcdsaSignature&, const EcdsaSignature&);
+void check(const EcdsaSignatureFuture&, const EcdsaSignatureFuture&);
+
+/**
+ * \brief create a random EcdsaSignature
+ * \param seed the optional seed for the RNG
+ * \return created signature
+ */
+EcdsaSignature create_random_ecdsa_signature(int seed = 0);
+
+namespace v2
+{
+
+void check(const Signature&, const Signature&);
+
+} // namespace v2
+} // namespace security
+} // namespace vanetza
+
+#endif /* CHECK_SIGNATURE_HPP_7RESWTUO */