Fix CPack component dependency graph

[VolkerChristian]

What changed

• correct the misspelled manually normalized net-un-phy component
• declare CPack dependencies for all physical network components
• declare CPack dependencies for all installed Express transport components
• declare CPack dependencies for MQTT-over-WebSocket components
• retain deterministic component enumeration across supported CMake versions

Why

The install rules create these components, but the CPack model did not describe their dependency relationships. With component-based Debian packaging enabled, that could produce incomplete package dependency metadata. The manually injected Unix-domain component was also misspelled as net-un-sphy-tream.

Validation

• branch is based directly on current master (77415c71a87fb7955e9a050bedaca02b65754324)
• reviewed the resulting one-file diff: 49 additions, 15 deletions
• component names and dependencies were matched against the corresponding installed targets and public link relationships

Full build/package validation is left to the repository CI because this change was made through the connected GitHub API rather than a local checkout.

[VolkerChristian]

Superseded by #228. The replacement implements the requested architecture: each component registers itself in its own CMakeLists.txt, while the shared CMake component API centrally generates runtime/development installation, exports, CPack metadata, dependency graphs, and validation.