added code for wellknown kusto endpoints

[tanmaya-panda1]

This pull request introduces a new mechanism for validating that Kusto endpoints are trusted, using a configurable set of rules loaded from a shared JSON file. The validation logic is enforced at client initialization, and is extensible for custom or additional trusted hosts. The changes include new utility classes for endpoint rule matching, data loading from JSON, and a custom exception for invalid endpoints. The build process is also updated to ensure the JSON file is available at runtime.

Endpoint trust validation and configuration:

• Added KustoTrustedEndpoints utility to validate Kusto endpoints against a set of trusted hostnames and suffixes, loaded from WellKnownKustoEndpoints.json. The logic allows for overrides and additional trusted hosts, and throws a custom exception if validation fails.
• Introduced FastSuffixMatcher for efficient hostname/suffix rule matching, and supporting data classes for rule and match result representation.
• Added WellKnownKustoEndpointsData for loading and parsing the trusted endpoints JSON file from the classpath, with robust error handling.
• Created KustoClientInvalidConnectionStringException for signaling invalid or untrusted endpoints.

Integration and enforcement in client initialization:

• Updated KustoBaseApiClient to validate the dmUrl endpoint on initialization unless security checks are explicitly skipped, using the new trusted endpoints logic. [1] [2]

Build process update:

• Modified ingest-v2/pom.xml to copy WellKnownKustoEndpoints.json from the data module into the build output, ensuring the trusted endpoints configuration is always available at runtime.### Added

Changed

Fixed

[github-actions]

Test Results

530 tests  ±0   521 ✅ ±0   7m 57s ⏱️ + 4m 33s
 31 suites ±0     9 💤 ±0 
 31 files   ±0     0 ❌ ±0 

Results for commit c5b6367. ± Comparison against base commit b9ccf14.

♻️ This comment has been updated with latest results.