Guard dataRegisters[]-bound registers created in OpenBuild against version-promotion side effects

[rubenvdlinde]

Problem

A register that is (a) created inside OpenBuild but (b) bound to an application via Application.dataRegisters[] rather than ApplicationVersion.register is an unusual, currently unguarded combination. Nothing prevents version promotion / release flows from treating such a shared register as version-scoped, and nothing marks it as "fed independently" (the data-registers-schema-declaration framing).

Proposal

Add a guard so that:

• a dataRegisters[]-bound register is never cloned/namespaced/touched by version promotion or release,
• the UI/API marks it as shared-and-independently-fed, distinct from the per-version registers the wizard creates.

Context: the hydra-console app (flows-first spec wave, 2026-07-27) uses exactly this shape — a thin hydra-cache register created in OpenBuild, bound via dataRegisters[], fed by OpenConnector synchronizations, rebuildable from the forge at any time.