SNOW-3488564: Remove Python 3.9

[sfc-gh-joshi]

1. Which Jira issue is this PR addressing? Make sure that there is an accompanying issue to your PR.

   Fixes SNOW-3488564

2. Fill out the following pre-review checklist:

   • I am adding a new automated test(s) to verify correctness of my new code
     • If this test skips Local Testing mode, I'm requesting review from @snowflakedb/local-testing
   • I am adding new logging messages
   • I am adding a new telemetry message
   • I am adding new credentials
   • I am adding a new dependency
   • If this is a new feature/behavior, I'm adding the Local Testing parity changes.
   • I acknowledge that I have ensured my changes to be thread-safe. Follow the link for more information: Thread-safe Developer Guidelines
   • If adding any arguments to public Snowpark APIs or creating new public Snowpark APIs, I acknowledge that I have ensured my changes include AST support. Follow the link for more information: AST Support Guidelines

3. Please describe how your code solves the related issue.

Removes support for Python 3.9, adjusting import guards/test skips as needed. Tox environments and github actions jobs that previously used 3.9 have been bumped to 3.10 or removed.

[sfc-gh-mayliu]

Snowpark-python specific python3.9 decommission changes look good; a few other places might also need updates. Another place I found is ReleaseSnowparkPythonPackageJob.groovy default release params still include 3.9. Can we drop that here too so the release job matches the supported matrix?

[sfc-gh-mayliu]

conda builds look right to drop 3.9. Do we need the matching Jenkins packaging update too? jenkins_utils' Snowpark BuildAnaconda.groovy still shells out with --python=3.9`, so shall we sync that as well?

[sfc-gh-joshi]

conda builds look right to drop 3.9. Do we need the matching Jenkins packaging update too? jenkins_utils' Snowpark BuildAnaconda.groovy still shells out with --python=3.9`, so shall we sync that as well?

That would make sense, but it looks like that file is also missing builds for 3.12, 3.13, and 3.14 entirely (which already exist in this repository's conda_build.sh). I'm not sure if that groovy file is still used anywhere.

[sfc-gh-mayliu]

It'd be great to trigger all relevant Jenkins jobs with this branch to monitor how Snowpark-python's 3.9 decommission impact downstream Jenkins builds. We could leverage this target: https://snowpark-python-001.jenkinsdev1.us-west-2.aws-dev.app.snowflake.com/job/SnowparkPythonReleaseValidationTrigger/

[sfc-gh-joshi]

I just kicked off a release validation run: https://snowpark-python-001.jenkinsdev1.us-west-2.aws-dev.app.snowflake.com/job/SnowparkPythonReleaseValidationTrigger/83/

Snowpark-python specific python3.9 decommission changes look good; a few other places might also need updates. Another place I found is ReleaseSnowparkPythonPackageJob.groovy default release params still include 3.9. Can we drop that here too so the release job matches the supported matrix?

It looks like this job was last run almost a year ago, do we know who's using it? https://snowpark-python-001.jenkinsdev1.us-west-2.aws-dev.app.snowflake.com/job/ArtifactRepository/job/ReleaseSnowparkPythonPackageJob/