PYTHON-4321 Add support for Python 3.13 and update changelog for 1.11.0 release

[blink1073]

No description provided.

[NoahStapp]

Is this really the only change we need to make to support 3.13? Wow!

[blink1073]

We had been testing in GitHub Actions, but now in EVG as well. 😄

[ShaneHarvey]

Are we testing Python 3.13 on evergreen?

[ShaneHarvey]

Also are the python test failures on Evergreen expected?

[blink1073]

One set of failures is fixed by mongodb-labs/drivers-evergreen-tools#487. I'm not sure why the one test is failing, I've yet to see a difference between this PR and https://spruce.mongodb.com/task/mongo_python_driver_tests_python_version_rhel8_test_encryption__platform~rhel8_auth_ssl~noauth_nossl_python_version~3.12_encryption~encryption_crypt_shared_test_8.0_sharded_cluster_4e74c8274e7c4cb7658d445d526dcc33ced1750b_24_09_04_12_58_14/logs?execution=0.

[ShaneHarvey]

Still think we should add 3.13 testing on evergreen if possible.

[blink1073]

Still think we should add 3.13 testing on evergreen if possible.

Yep, I have that done locally, I'm running patch builds to figure out the test failure.

[blink1073]

Okay, I found the issue: we need to use the same version of crypt_shared, the one downloaded during run-orchestration.sh.

[ShaneHarvey]

Still need to add 3.13 here: https://github.com/mongodb/libmongocrypt/blob/master/bindings/python/.evergreen/test.sh

[blink1073]

Still need to add 3.13 here: master/bindings/python/.evergreen/test.sh

Done

[ShaneHarvey]

Note the test_fork failure is tracked by https://jira.mongodb.org/browse/PYTHON-4738.