Add Python 3.12 and 3.13 support

[Dhanush010]

• Add Python 3.12 and 3.13 to package classifiers
• Update CI/CD workflows to test against Python 3.12 and 3.13
• Add Gradle test tasks for Python 3.12 and 3.13 (MySQL and PostgreSQL)
• Update Java and Python enum types to include 3.12 and 3.13
• Add Docker image mappings for Python 3.12 and 3.13
• Update documentation to reflect Python 3.8-3.13 support

Resolves #967

Description

 This PR adds support for Python 3.12 and 3.13 to the AWS Advanced Python Wrapper.
 
 ## Changes
 - Added Python 3.12 and 3.13 to package classifiers in `pyproject.toml`
 - Updated CI/CD workflows to test against Python 3.12 and 3.13
 - Added Gradle test tasks for Python 3.12 and 3.13 (MySQL and PostgreSQL variants)
 - Updated Java and Python enum types to include Python 3.12 and 3.13
 - Added Docker image mappings for Python 3.12 and 3.13
 - Updated documentation to reflect Python 3.8-3.13 support
 
 ## Testing
 - All 13 files verified
 - No linting errors
 - Syntax validated
 
 Resolves #967

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[Dhanush010]

Hi maintainers, this PR adds Python 3.12 and 3.13 support across classifiers, CI matrices, integration test tasks, enums, Docker images, and docs (Resolves #967). Could you please approve and run the workflows and review when you have a moment? I’ve updated the branch and verified locally. Thanks!

[karenc-bq]

Thank you for your efforts @Dhanush010!

[Dhanush010]

Hi @karenc-bq,
I fixed the Python 3.12+ test failures. The issue was that Python 3.12+ has stricter isinstance() checks with Protocols, so I replaced MagicMock with real AuroraPgDialect() instances in the test fixtures.
Python 3.8-3.11 tests are passing. The branch is updated with the latest upstream changes and ready for review. Could you please review it when you have time, Thank you.

[karenc-bq]

Hi @Dhanush010, thank you for your contribution. We’ve resolved the merge conflicts and incorporated your changes via a separate PR, which is now available in version 2.0.0. Please give it a try and let us know if you encounter any issues. Thanks again for your interest and support!