[Yadan-Wei]

Issue #, if available:

Description of changes:

Adds eight registries to the TensorFlow inference 2.20.0 image URI config: sa-west-1, me-west-1, eusc-de-east-1, eu-isoe-west-1, us-iso-east-1, us-isob-east-1, us-isof-east-1 and us-isof-south-1. With them, image_uris.retrieve() resolves the image in these regions. Each account matches the region's existing entry for TensorFlow training 2.21.0, which already lists all eight.

The automated image URI config updates don't produce TensorFlow inference 2.20 entries, so these regions were never added. Only these eight registry entries change; the rest of the file is untouched.

Testing done:

• pytest tests/unit/image_uris in sagemaker-core: 277 passed, 2 skipped.
• image_uris.retrieve("tensorflow", version="2.20.0", image_scope="inference", py_version="py312") returns the expected CPU and GPU URIs in the new regions, for example 434457397001.dkr.ecr.sa-west-1.amazonaws.com/tensorflow-inference:2.20.0-cpu-py312.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[github-actions]

🤖 AI code review

This PR adds eight partition registries (sa-west-1, me-west-1, eusc-de-east-1, eu-isoe-west-1, us-iso-east-1, us-isob-east-1, us-isof-east-1, us-isof-south-1) to the TensorFlow inference 2.20.0 entry in tensorflow.json. I verified each added account ID matches exactly the corresponding region in the TensorFlow training 2.21.0 entry (lines 5158, 5165, 5169, 5172, 5177–5180), the keys are inserted in alphabetical order consistent with the existing file, and the change is data-only. These same registry account IDs match prior precedent (e.g., me-west-1: 124382933778, eu-isoe-west-1: 371248457586) from the partition-registry rollout PRs. The change looks correct and I found no issues.

_{Reviewed commit 835e2d4. Automated review; verify before acting.}