fix: adding auto resolution config support

[tanvikab]

fix: adding auto resolution config support #5256

The JumpStart inference configuration auto-detection problem occurred because users had to manually specify the config_name parameter when deploying models to different instance types, leading to deployment failures when GPU configurations were incorrectly applied to Neuron instances or vice versa. The root cause was that four critical artifact retrieval functions (image_uris.py, model_uris.py, environment_variables.py, and resource_requirements.py) lacked auto-detection logic, causing the system to default to the first available configuration instead of selecting the appropriate one for the target instance type.

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)
• [ ] If adding any dependency in requirements.txt files, I have spell checked and ensured they exist in PyPi

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

[zhaoqizqwang]

Hi, as part of incoming PySDK V3 release, master branch will be replaced by PySDK V3 code. We have changed the target branch to master-v2