fix: Master release bug fixes

[BrendanWalsh]

Summary

Backports critical bug fixes from the Spark 4.0 release testing to master.

Changes

1. Azure Maps Spatial API Retired (9/30/2025)

• CheckPointInPolygon.scala: Throws UnsupportedOperationException on transform()
• AzureMapsSuite.scala: Removed AzMapsPointInPolygonSuite test class
• FuzzingTest.scala: Added exemptions for CheckPointInPolygon

2. PEP 440 Python Version Normalization

• build.scala: pythonizedVersion now uses + local version separator and .toLowerCase() to match pip/wheel filename normalization

3. Conda Environment Activation

• build.scala: activateCondaEnv now uses conda run on Linux to ensure correct environment

4. Language API Version Update

• AnalyzeTextSuite.scala, AnalyzeTextLROSuite.scala: Updated from retired 2022-10-01-preview to 2024-11-01

5. R Tests Local Jar Loading

• RTestGen.scala: Loads all module jars locally instead of relying on Maven resolution of potentially unpublished SNAPSHOTs

Testing

Verified against spark4.0 branch where these fixes have passed CI.

Related

• Azure Maps retirement: https://azure.microsoft.com/en-us/updates/v2/azure-maps-creator-services-retirement-on-30-september-2025

[github-actions]

Hey @BrendanWalsh 👋!
Thank you so much for contributing to our repository 🙌.
Someone from SynapseML Team will be reviewing this pull request soon.

We use semantic commit messages to streamline the release process.
Before your pull request can be merged, you should make sure your first commit and PR title start with a semantic prefix.
This helps us to create release messages and credit you for your hard work!

Examples of commit messages with semantic prefixes:

• fix: Fix LightGBM crashes with empty partitions
• feat: Make HTTP on Spark back-offs configurable
• docs: Update Spark Serving usage
• build: Add codecov support
• perf: improve LightGBM memory usage
• refactor: make python code generation rely on classes
• style: Remove nulls from CNTKModel
• test: Add test coverage for CNTKModel

To test your commit locally, please follow our guild on building from source.
Check out the developer guide for additional guidance on testing your change.

[BrendanWalsh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[codecov-commenter]

Codecov Report

❌ Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 84.23%. Comparing base (baf63dc) to head (d2a9dde).

Files with missing lines	Patch %	Lines
...e/ml/services/geospatial/CheckPointInPolygon.scala	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2485      +/-   ##
==========================================
- Coverage   84.43%   84.23%   -0.21%     
==========================================
  Files         335      335              
  Lines       17779    17781       +2     
  Branches     1603     1592      -11     
==========================================
- Hits        15012    14978      -34     
- Misses       2767     2803      +36     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[BrendanWalsh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).