Fix: When editing MCP custom 'crossplane' providers should be preserved

[lucasgoral]

What this PR does / why we need it:

When editing MCP custom 'crossplane' providers should be preserved

[Copilot]

Pull request overview

This PR fixes an issue where custom crossplane providers were not being preserved when editing a Managed Control Plane (MCP). The solution introduces an explicit isProvider field to the ComponentsListItem interface and implements logic to preserve custom providers from the initial selection that may no longer be in the available components list.

Key changes:

• Added isProvider boolean field to ComponentsListItem interface to replace string-matching logic for identifying providers
• Implemented preservation logic for custom providers from initialSelection that don't exist in the available components list
• Centralized component sorting logic in useComponentsSelectionData hook to ensure providers are consistently positioned after crossplane

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/lib/api/types/crate/createManagedControlPlane.ts	Added isProvider field to ComponentsListItem interface and updated filter logic to use the new field instead of string matching
src/components/Wizards/CreateManagedControlPlane/useComponentsSelectionData.ts	Set isProvider field when building components list, added logic to preserve custom providers from initialSelection, and implemented sorting to position providers after crossplane
src/components/ComponentsSelection/ComponentsSelection.tsx	Removed local isProvider callback and sorting logic in favor of using pre-sorted data with component.isProvider field; also alphabetically sorted imports

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[andreaskienle]

Tested it, fixes the issue.

Here's a follow-up task to clean things up: openmcp-project/backlog#399