As a developer,
I want to extract the logic for determining the Console configuration with dynamic plugins from the Console Operator and move it into the Console backend,
so that we can avoid unnecessary redeployments of the Console pod when dynamic plugin configuration changes.

Acceptance Criteria:

• The logic that computes dynamic plugin configuration (e.g., enabled plugins, i18n, proxy settings) is relocated from the Console Operator to the Console backend.

• The console-config ConfigMap should no longer contain dynamic plugin-specific configuration.

• The Console backend must dynamically compute and serve the plugin configuration on startup or request.

• The Console Operator should no longer trigger Console pod redeployment due to changes in dynamic plugin configuration.

• The solution must maintain backward compatibility with existing plugin lifecycle (e.g., enable/disable flows).

• Tests are updated to reflect the new configuration flow.

Technical Notes:

• Ensure that the new implementation in the backend has access to the required CRs or annotations (e.g., ConsolePlugin CRs).

• If needed, introduce a new API endpoint for fetching plugin configuration dynamically at runtime.

• Coordinate with QE to validate that plugin behavior remains unchanged across various cluster states.