fix(techvault): materialize detection content and SOC ports

[Brad-Edwards]

Summary

• package the Wazuh rule and decoder corpora that TechVault declares as loaded
• materialize those assets at the manager paths referenced by its generated configuration
• preserve the executable Wazuh-to-Shuffle integration as a pack directory artifact
• restore loopback-only host publications for MISP, TheHive, Cortex, and Shuffle
• align the lockfile with the existing 3.9.0 package version
• add regression tests for loaded content placements, executable integration content, and SOC port exposure

Problem

A clean env-pack realization started the full TechVault topology, but the Wazuh manager could not find any declared custom rule files and participant-facing SOC services had no host bindings. The web attack reached TechVault but produced zero custom alerts, and TheHive was reachable only through a changing Docker bridge address.

Validation

• full unittest suite: 814 tests passed
• repository and pack content validation passed
• all release gates passed
• source and test compile checks passed
• uv lock consistency check passed