Providers mapping bug fix

[Hubert-Szczepanski-SAP]

Fixes openmcp-project/backlog#279

[Copilot]

Pull Request Overview

This PR fixes a bug in provider mapping by refactoring how provider types are resolved. Instead of looking up provider configurations by name and checking apiVersion patterns, it now directly extracts and normalizes the domain from the apiVersion string.

Key changes:

• Replaced resolveProviderType function with resolveProviderTypeFromApiVersion that extracts domain from apiVersion
• Removed dependency on providerConfigsList parameter in the resolution logic
• Updated test suite to reflect the new function signature and behavior

Reviewed Changes

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

File	Description
src/components/Graphs/graphUtils.ts	Refactored provider type resolution to extract domain directly from apiVersion instead of iterating through provider configs
src/components/Graphs/graphUtils.spec.ts	Updated tests to validate domain extraction and "account." prefix removal logic

---

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

[Copilot]

The fallback to empty string is ineffective because split('/')[0] will never return undefined or null. If apiVersion is an empty string, split('/')[0] returns an empty string. If apiVersion is undefined or null, this will throw an error. Consider adding a guard: const domain = apiVersion?.split('/')[0] || ''; or handle the undefined/null case before splitting.

Suggested change

	const domain = apiVersion.split('/')[0] || '';
	const domain = apiVersion?.split('/')[0] || '';

[andreaskienle]

Check out Copilot's comment. I think it makes sense to safeguard against null/undefined being passed even though we have TypeScript. It's just a small change and an extra test.

Apart from that: 👍🏻