Separate migration tests from regular builds

[aws-sdk-java-automation]

Motivation and Context

Add migration-test Maven profile and excludev2-migration-tests in regular builds. This can reduce 20+ mins and speed up the build. A separate CB will be created to run those tests in parallel.

Previous changes for endpoint tests:
#3553 & #4860

Modifications

Testing

Tested locally:

mvn install -pl :v2-migration-tests -> tests skipped

mvn install -pl :v2-migration-tests -P migration-test -> tests ran

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
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[davidh44]

closing to open new PR, accidentally opened with automation account