Gracefully handle invalid ReleaseChannel Version in MCP

[sdischer-sap]

Context

When a provider is installed in an MCP and we remove the version which is installed from our releasechannel, the following error is displayed in MCP resource:

Managed By:            CloudOrchestrator
    Message:               The ControlPlane resource is not ready yet.
The following ControlPlane conditions are not 'True':
  ProviderCloudfoundryReady: ProviderCloudfoundry not installable: Component provider-cloudfoundry with version 2.3.0 not found.

    Reason:                WaitingForCloudOrchestrator
    Status:                False
    Type:                  CloudOrchestratorHealthy

This does not display the correct status, as the provider is still running and should still run, but can just not be installed anymore. This came up initially with removing a faulty CF 2.3.0 release, but will more likely by a regular requirement going forward.

Issue created as result of a dev-sync discussion on 2. april 2025

Acceptance

• Reflect a proper error message, ideally showing the last possible version to choose
• Distinguish between critical and none critical errors to not Fail the overall MCP status in case of only non-critical errors
  • Non-critical errors should not have an impact on the Ready condition of the MCP