test: Added support for Python 3.13 to tests

[hbelmiro]

Description of your changes:
This PR adds support for Python 3.13 to tests. This is a follow-up for #11372

Checklist:

• You have signed off your commits
• The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

[google-oss-prow]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from hbelmiro and additionally assign connor-mccarthy for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• .github/OWNERS
• api/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hbelmiro]

@chensun we have several tests failing with Python 3.13. Can you please take a look?
Also, I think we should have all tests using at least the minor and major supported Python versions (3.9 and 3.13).

cc @DharmitD @HumairAK

[chensun]

@chensun we have several tests failing with Python 3.13. Can you please take a look?

From SDK side, kfp-pipeline-spec is blocking Python 3.13 support. I sent a PR: #11378, PTAL.

Also, I think we should have all tests using at least the minor and major supported Python versions (3.9 and 3.13).

No, I think it would be unnecessary and waste of resource to run all e2e or backend-integration tests with different Python versions. If we think SDK's main role as a YAML generator, as long as the produced YAML file doesn't change across Python versions--the SDK unit test guarantees that--they would work on the backend.