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

@@ -0,0 +1,98 @@
+#ifndef VERIFY_SERVICE_HPP_BR4ISDBH
+#define VERIFY_SERVICE_HPP_BR4ISDBH
+
+#include <boost/optional.hpp>
+#include <vanetza/common/its_aid.hpp>
+#include <vanetza/security/certificate_validity.hpp>
+#include <vanetza/security/hashed_id.hpp>
+#include <vanetza/security/secured_message.hpp>
+
+namespace vanetza
+{
+namespace security
+{
+
+/**
+ * SN-VERIFY.confirm report codes
+ * 
+ * "Configuration_Problem" is not found in TS 103 723-8 V1.1.1 but indicates a
+ * problem with the verification subsystem itself, e.g. a programming error.
+ * 
+ * \see TS 102 723-8 v1.1.1 table 5
+ */
+enum class VerificationReport
+{
+    Success,
+    False_Signature,
+    Invalid_Certificate,
+    Revoked_Certificate,
+    Inconsistent_Chain,
+    Invalid_Timestamp,
+    Duplicate_Message,
+    Invalid_Mobility_Data,
+    Unsigned_Message,
+    Signer_Certificate_Not_Found,
+    Unsupported_Signer_Identifier_Type,
+    Incompatible_Protocol,
+    Configuration_Problem,
+};
+
+// mandatory parameters of SN-VERIFY.request (TS 102 723-8 V1.1.1)
+struct VerifyRequest
+{
+    VerifyRequest(SecuredMessageView msg) : secured_message(msg) {}
+    SecuredMessageView secured_message; /*< contains security header and payload */
+};
+
+// parameters of SN-VERIFY.confirm (TS 102 723-8 V1.1.1)
+struct VerifyConfirm
+{
+    VerificationReport report; // mandatory
+    ItsAid its_aid; // mandatory
+    ByteBuffer permissions; // mandatory
+    CertificateValidity certificate_validity; // non-standard extension
+    boost::optional<HashedId8> certificate_id; // optional
+};
+
+/**
+ * Equivalent of SN-VERIFY service in TS 102 723-8 V1.1.1
+ */
+class VerifyService
+{
+public:
+    virtual ~VerifyService() = default;
+    virtual VerifyConfirm verify(const VerifyRequest&) = 0;
+};
+
+// forward declaration
+namespace v3 { class CertificateCache; }
+
+/**
+ * Get insecure dummy verify service without any checks
+ */
+class DummyVerifyService : public VerifyService
+{
+public:
+    /**
+     * \param report predefined confirm report result
+     * \param validity predefined certificate validity result 
+     */
+    DummyVerifyService(VerificationReport report, CertificateValidity validity);
+    VerifyConfirm verify(const VerifyRequest&) override;
+
+    /**
+     * \brief register certificate cache for optional permission lookup
+     * \param cache certificate cache
+     */
+    void use_certificate_cache(v3::CertificateCache* cache);
+
+private:
+    VerificationReport m_report;
+    CertificateValidity m_validity;
+    v3::CertificateCache* m_cert_cache = nullptr;
+};
+
+} // namespace security
+} // namespace vanetza
+
+#endif /* VERIFY_SERVICE_HPP_BR4ISDBH */