[Bug]: LLM Provider version validation issue

[ashera96]

Please select the area the issue is related to

Area/Management (Management API or Management Portal UI)

Please select the aspect the issue is related to

Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)

Description

Even though a version validation exists at the creation step, update path does not enforce the same.

Creation step validation:

Once created, can be edited to a previously failed version like so:

Steps to Reproduce

1. Create LLM Provider using version v1.0
2. Update the provider version from the overview to 0.9
3. Notice the successful update call response

Severity Level of the Issue

Severity/Minor (Non-critical functionality. Can be fixed in future releases)

Environment Details (with versions)

No response

[Tharanidk]

Provider version can be edited to any value. Validation should be added in the edit flow as well

[Induwara04]

I think the best practice here is to remove version from all update payloads instead of adding version validation to every update path.

The reason is that provider/API versioning should be treated as a separate creation-time concept. Once an LLM Provider is created with a specific version, regular update operations should only modify editable metadata/configuration fields, not the version itself.

If users need a different version, we should provide a dedicated Create New Version feature instead of allowing the version to be modified through the update API.