[FEATURE] ate-setup install record merges partial deploys and stores Components #3688

The install record is replaced on every run, so a partial deploy drops earlier settings, including sizing, and the upgrade runbook replays whatever the last run wrote. Implement the install record changes in the ate-setup interface contract (#3189).

Tracks "Keep sizing in the install record" in the Operator Supplied Values workstream of the Extensible Install Roadmap.

Current state (0b635b80): cmd/ate-setup/internal/config/record.go rewrites the record from the current run's settings only.

Required changes

• Store --component paths in the record (absolute, in flag order).
• A later deploy merges into the record instead of replacing it.
• --unset <key> and --remove-component <dir> remove entries.
• Keys for removed settings are dropped when the record is rewritten.

Dependencies: #3167 (--component).

Breaking change: yes. Omitted settings now mean "keep the recorded value". Release note required.

Enforcement: CLI tests for merge, --unset, --remove-component, and dropping removed keys. Once the record carries Components, #3313 can drop "pass --component on every step".

Parent Issue: #3165