Keep vanetza-idf in obu-firmware, so a plain clone builds the firmware

obu-firmware builds against the vanetza-idf C-ITS library, which until now
came from the colleague's microbu-esp32c5 tree beside the repository and was
not tracked here, so a clone of this repository could not build the firmware
it ships. The library alone is now part of obu-firmware, as
obu-firmware/external/vanetza-idf: their external/vanetza-idf at commit
cf4b99f, unchanged (9775 files; see its PROVENANCE.md). CMake takes it from
there by default; -DVANETZA_IDF_DIR still points the build elsewhere.

The rest of the colleague's tree (their own VAM firmware, PKI tooling,
station-link Python tools, the V2X2MAP bridge) stays out of this repository
and gitignored; nothing is pushed to their repository. NOTES.md, docs/06,
TODO.md and the pcap verifier's usage line point at the new location.

obu-firmware/external/vanetza-idf/vanetza/security/v2/certificate_provider.hpp

@@ -0,0 +1,43 @@
+#ifndef A137DCCA_FFB9_4D91_8441_D559E6F17C14
+#define A137DCCA_FFB9_4D91_8441_D559E6F17C14
+
+#include <vanetza/security/ecdsa256.hpp>
+#include <vanetza/security/v2/certificate.hpp>
+#include <list>
+
+namespace vanetza
+{
+namespace security
+{
+namespace v2
+{
+
+class CertificateProvider
+{
+public:
+    /**
+     * Get own certificate to use for signing
+     * \return own certificate
+     */
+    virtual const Certificate& own_certificate() = 0;
+
+    /**
+     * Get own certificate chain in root CA → AA → AT order, excluding the AT and root certificate
+     * \return own certificate chain
+     */
+    virtual std::list<Certificate> own_chain() = 0;
+
+    /**
+     * Get private key associated with own certificate
+     * \return private key
+     */
+    virtual const ecdsa256::PrivateKey& own_private_key() = 0;
+
+    virtual ~CertificateProvider() = default;
+};
+
+} // namespace v2
+} // namespace security
+} // namespace vanetza
+
+#endif /* A137DCCA_FFB9_4D91_8441_D559E6F17C14 */