Console silently converts CORS origins to regex format in application edit section

[ThaminduDilshan]

Description

From the /server-config/cors API, origins like below are rejected.

https://example.com/path
https://example.com?x=1
https://example.com#frag

However, when the same origins are added from the console, console converts them to regexes (like {"regex":"https://example.com/path"}) and send them in the PUT request, which is getting successful. This behavior obscures user intent and can introduce failures where strict origin matching is required.

Related: #4721

Steps to Reproduce

1. Login to console
2. Create an application
3. Try to configure allowed origins

Version

v1.0.0-beta2

Environment Details (with versions)

No response

[ThaminduDilshan]

As per the discussion;

• We should not silently convert application allowed origins to regexes
• If possible, give the option to mark it as regex explicitly. We don't need a regex validator for now

IMO we should make this behaviour consistent in both application allowed origin configurations and server settings section