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/tools/pki/sha.hpp

@@ -0,0 +1,27 @@
+#pragma once
+
+#include <vanetza/security/hash_algorithm.hpp>
+#include <array>
+#include <cstdint>
+
+namespace vanetza
+{
+namespace pki
+{
+
+using security::HashAlgorithm;
+
+struct Sha256Hash
+{
+    static constexpr std::size_t length = 32;
+    std::array<std::uint8_t, length> octets;
+};
+
+struct Sha384Hash
+{
+    static constexpr std::size_t length = 48;
+    std::array<std::uint8_t, length> octets;
+};
+
+} // namespace pki
+} // namespace vanetza