chore(parameters): deprecate ParamConfigRenderer by moving bindings into ParametersDefinition

[leon-ape]

Summary

This PR deprecates ParamConfigRenderer from the runtime path and moves component parameter binding metadata into ParametersDefinition.

After this change:

• runtime resolves bindings directly from ParametersDefinition
• base templates are always rerendered before applying parameter updates
• runtime no longer depends on Payload / reRenderResourceTypes
• legacy ParamConfigRenderer remains supported through fallback compatibility logic

Why

The old model had two main issues:

1. ParamConfigRenderer added an extra indirection in the runtime chain:

   • Component -> ComponentDefinition -> ParamConfigRenderer -> ParametersDefinition

2. conditional rerendering depended on limited trigger metadata, while templates actually rendered from live component state, which could make final config depend on event order instead of current state.

This PR simplifies the model and makes config rendering behave more like a normal reconcile loop.

Main Changes

• Added binding metadata to ParametersDefinition:

  • componentDef
  • serviceVersion
  • templateName
  • fileName
  • fileFormatConfig

• Changed runtime resolution from:

  • Component -> ComponentDefinition -> ParamConfigRenderer -> ParametersDefinition
    to:
  • Component -> ComponentDefinition -> matched ParametersDefinitions

• Removed conditional rerender gating and always rerender the base template before applying parameter patches

• Removed runtime dependency on Payload / reRenderResourceTypes

• Made ComponentParameter react directly to Component changes by watching Component and comparing applied Component.Generation

• Removed the legacy ParamConfigRenderer controller from runtime registration

Compatibility

Backward compatibility is preserved.

• Old addons and old instances that still use ParamConfigRenderer are supported through fallback
• New addons can use direct ParametersDefinition bindings
• Mixed migration is supported:
  • if some files are defined by new PD and others still come from legacy PCR, runtime merges them by file
  • if both define the same file, new PD wins

Other compatibility notes:

• legacy fallback no longer depends on ParamConfigRenderer.status.phase
• ParamConfigRenderer API/CRD is retained and marked deprecated
• RBAC keeps the read permissions needed for legacy fallback

Tests

Added and updated coverage for:

• direct ParametersDefinition binding resolution
• legacy fallback
• mixed new PD + legacy PCR resolution
• same-file conflict where new PD overrides legacy PCR
• malformed unrelated legacy PCR not breaking fallback
• controller-level mixed-mode rendering
• rerender on component change
• always-rerender-before-apply behavior

Also tightened controller test fixtures to avoid cache timing races and flaky ComponentParameter not found failures.

Follow-up

This PR keeps the deprecated ParamConfigRenderer API only for compatibility.

A later cleanup PR can remove the remaining compatibility surface after addon migration is complete.

[codecov]

Codecov Report

❌ Patch coverage is 52.67857% with 159 lines in your changes missing coverage. Please review.
✅ Project coverage is 51.74%. Comparing base (edbff89) to head (1281398).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/parameters/config_util.go	49.41%	64 Missing and 23 partials ⚠️
...estutil/parameters/parametersdefinition_factory.go	0.00%	24 Missing ⚠️
pkg/parameters/config_metadata.go	13.33%	13 Missing ⚠️
pkg/parameters/parameter_utils.go	55.55%	4 Missing and 4 partials ⚠️
.../parameters/componentparameter_controller_utils.go	69.56%	2 Missing and 5 partials ⚠️
...ollers/parameters/componentparameter_controller.go	64.70%	4 Missing and 2 partials ⚠️
pkg/parameters/core/config_patch_util.go	50.00%	4 Missing ⚠️
controllers/parameters/reconfigure_controller.go	50.00%	1 Missing and 2 partials ⚠️
...ntrollers/parameters/parameter_controller_utils.go	60.00%	1 Missing and 1 partial ⚠️
pkg/parameters/core/reconfigure_util.go	0.00%	2 Missing ⚠️
... and 2 more

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10100      +/-   ##
==========================================
+ Coverage   51.60%   51.74%   +0.13%     
==========================================
  Files         525      525              
  Lines       58397    58243     -154     
==========================================
+ Hits        30138    30140       +2     
+ Misses      25305    25148     -157     
- Partials     2954     2955       +1     

Flag	Coverage Δ
unittests	51.74% <52.67%> (+0.13%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[leon-ape]

/approve