feat: triton v24.09

[maaquib]

Issue #, if available:

Description of changes:

Testing done:

Merge Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.

General

• I have read the CONTRIBUTING doc
• I certify that the changes I am introducing will be backward compatible, and I have discussed concerns about this, if any, with the Python SDK team
• I used the commit message format described in CONTRIBUTING
• I have passed the region in to all S3 and STS clients that I've initialized as part of this change.
• I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added unit and/or integration tests as appropriate to ensure backward compatibility of the changes
• I have checked that my tests are not configured for a specific region or account (if appropriate)
• I have used unique_name_from_base to create resource names in integ tests (if appropriate)

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

[bhadrip]

Why do we keep repeating the aws accounts for each version ? are we expecting the versions to not be available in a given region ?

[maaquib]

Why do we keep repeating the aws accounts for each version ? are we expecting the versions to not be available in a given region ?

Not really sure. This is the convention that I see across all config files. If you guys have a better way, I'm happy to adopt it

[bhadrip]

@nargokul do you have any insights in this image formats ?

[bhadrip]

approving it for now, we should refactor the image discovery feature. @nargokul can add more context on the future direction.