Fix: Authentication fails for entities with 'version' in name

[randreucetti]

Fixes #24718

Changes

• Replace overly broad substring check contains("version") with specific endpoint check
• Now only skips auth for /system/version endpoint, not all URLs containing "version"
• Add comprehensive unit tests

Problem

The authentication provider was skipping auth headers for any URL containing "version" as a substring, including:

• Entity names like "data-conversion-service" (contains "version" in "conversion")
• Entity names like "dataset-version-tracker"

Solution

Changed the check from:

if (requestTemplate.url().contains("version")) {
  return;
}

To:

String url = requestTemplate.url();
if (url.endsWith("/system/version") || url.contains("/system/version?")) {
  return;
}

This ensures only the actual version endpoint skips authentication, not every URL with "version" in it.

Testing

Added unit tests that verify:

• Auth headers ARE added for entities with "conversion", "version", etc. in their names
• Auth headers are NOT added for the /system/version endpoint
• Auth headers are NOT added for /system/version?param=value

[github-actions]

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!