Use partitions.json to generate Region class

[S-Saranya1]

Updated Region class generation to use Partitions.json instead of the Endpoints.json and removed the hardcoded global regions.

Motivation and Context

• Currently we are using deprecated endpoints.json to generate Region class and using hardcoded global regions.
• Switching to use partisions.json.resource to generate Region class which contains all regions.

Modifications

• Updated Region class generation to use partisions.json.resource file
• Removed the hardcoded global regions
• Added tests

Testing

• Added unit tests to verify the correct generation of global regions.
• After code generation, confirmed that all regions, including global ones, were properly generated from partisions.json.

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[sonarqubecloud]

Quality Gate passed

Issues
21 New issues
0 Accepted issues

Measures
0 Security Hotspots
82.6% Coverage on New Code
0.1% Duplication on New Code

See analysis details on SonarQube Cloud