Story 5.5 — Implement ConsensusConfig CR creation from data/config/ scan

**Epic:** #502 — Network Upgrade Workflow (Execute Phase)

Scan the `data/config/` directory in the deployment package and create one dedicated ConsensusConfig CR
per recognised config file.

**Acceptance criteria:**
- Use a hardcoded filename-to-CR-kind mapping (e.g. `log4j2.xml` → `Log4j2Config`, `settings.txt` → `NodeSettings`, `throttles.json` → `ThrottleConfig`). The full mapping + CR spec/GVR/label/status contract comes from solo-operator (see blocker).
- Determine the capsule name by querying the orbit namespace for the `ConsensusCapsule` CR and matching on the node-id label; use it for `metadata.name` and the `hedera.com/capsule` label. `spec.orbit` comes from the Execute CR.
- Reject unrecognised filenames with a `ConfigCRFailed` event; do not silently skip.
- Apply the `hedera.com/operation-id` label to every CR created.
- Emit `ConfigCRCreated` per CR.

**Blocked on:** solo-operator CRD contract (finalized filename→kind table, GVRs, spec/label/status field paths).