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/tests/check_certificate.cpp

@@ -0,0 +1,29 @@
+#include <gtest/gtest.h>
+#include <vanetza/security/v2/tests/check_certificate.hpp>
+#include <vanetza/security/v2/tests/check_list.hpp>
+#include <vanetza/security/v2/tests/check_signature.hpp>
+#include <vanetza/security/v2/tests/check_signer_info.hpp>
+#include <vanetza/security/v2/tests/check_subject_attribute.hpp>
+#include <vanetza/security/v2/tests/check_subject_info.hpp>
+#include <vanetza/security/v2/tests/check_validity_restriction.hpp>
+
+namespace vanetza
+{
+namespace security
+{
+namespace v2
+{
+
+void check(const Certificate& expected, const Certificate& actual)
+{
+    // certificate version is static, no check required
+    check(expected.signer_info, actual.signer_info);
+    check(expected.subject_info, actual.subject_info);
+    check(expected.subject_attributes, actual.subject_attributes, "SubjectAttribute");
+    check(expected.validity_restriction, actual.validity_restriction, "ValidityRestriction");
+    check(expected.signature, actual.signature);
+}
+
+} // namespace v2
+} // namespace security
+} // namespace vanetza