Task: B5: Implement supported/target set model for physical space binding

The address hierarchy is ores.{technical_space}[.{facet}[.{archetype}]].enabled:

Specificity resolution: more-specific address overrides less-specific. :ores.cpp.enabled: true + :ores.cpp.qt.enabled: false → S_e includes all C++ facets except Qt. This replicates Dogen's :masd.cpp.enabled: / :masd.csharp.enabled: semantics exactly.

# Generate everything the entity supports (T = S_e)
./projects/ores.codegen/codegen.sh generate --component refdata

# Generate only the sql technical space (T = all sql archetypes)
./projects/ores.codegen/codegen.sh generate --component refdata --address sql

# Generate only the qt facet (T = cpp.qt archetypes)
./projects/ores.codegen/codegen.sh generate --component refdata --address cpp.qt

--profile is removed. The entity's ores.* binding IS the profile; --address is only a filter, never an expansion. Updating all existing compass commands and skills to remove --profile invocations is in scope.

For hierarchical address resolution, the TS→facet map lives in a new * Technical spaces section of facet_catalogue.org (single authoritative source):

• Add * Technical spaces section to facet_catalogue.org.
• Implement in a dedicated module (codegen/physical_space.py):
  • compute_supported_set(properties, facet_catalogue, model_type) -> frozenset[str] — resolves ores.* properties with specificity ordering into a set of facet names for this entity.
  • compute_target_set(address, facet_catalogue) -> frozenset[str] — expands a CLI address to the matching set of facet names; raises on unknown address.
  • resolve_generation_set(supported, target) -> frozenset[str] — returns supported ∩ target; warns if the intersection is empty.
• Not inline in core.py or generator.py — keep generation-set logic independently testable.
• Remove --profile from the CLI arg parser; add --address (optional).
• Scan and update all compass commands and skills that pass --profile.

• Entity with :ores.cpp.enabled: false → S_e excludes all C++ facets; SQL output only.
• Entity with :ores.cpp.qt.enabled: false → S_e includes all C++ facets except Qt.
• Combined: :ores.cpp.enabled: true + :ores.cpp.qt.enabled: false → S_e = all C++ except Qt (more-specific address wins).
• Entity with no ores.* properties → S_e = all archetypes matching model-types filter (backward-compatible; no regression).

• Running with no --address → generates all of S_e (T = S_e).
• Running --address sql → T = all sql facets; generates T ∩ S_e.
• Running --address cpp for entity with :ores.cpp.enabled: false → T ∩ S_e = ∅; warning emitted; run continues for other entities.
• Running --address UNKNOWN → error (unknown address not in facet catalogue).

• --profile argument is removed from the codegen CLI.
• All existing compass commands and skills updated to remove --profile invocations.
• --address (optional) replaces --profile as the generation scope filter.

• facet_catalogue.org has a * Technical spaces section mapping each TS to its member facets; loaded by generator.py at startup.

• All supported/target set logic lives in codegen/physical_space.py — zero logic inline in core.py or generator.py.
• Unit tests cover every combination: no properties (backward compat), TS-level disable, facet-level disable, combined TS-enable + facet-disable override, target ⊆ supported (normal filter), target ∩ supported = ∅ (warn path), target completely outside supported (warn), unknown --address (error path). Test file: tests/test_physical_space.py.
• All existing regression tests pass.