For #29052 .

Changes proposed in this pull request:

• Change the execution phase of NativeTest under GraalVM Native Image from test to integration-test. This is a review of Fix the bug that nativeTest test suite cannot recognize modules without source code #35959 and Add support for running integration tests with Maven graalvm/native-build-tools#740 .
• Before this PR, the profile of nativeTestInShardingSphere changed the binding phase of maven-jar-plugin:jar from package to test, which broke some conventions of the Maven lifecycle and caused the third-party Maven plugin to misjudge some things. For the jar goal of org.eclipse.transformer:transformer-maven-plugin introduced in Add optional module for Jakarta Transactions impl of Jakarta EE 9 Spec #35810, this further caused the jar of the required sourceless module to not be successfully created in the test phase, because the jar goal of org.eclipse.transformer:transformer-maven-plugin again eliminated the configuration of maven-jar-plugin. We can't use the transform goal of org.eclipse.transformer:transformer-maven-plugin because we didn't actually configure what maven-jar-plugin does. See Native Build Tools cannot recognize Maven modules that only have pom.xml but no source code graalvm/native-build-tools#727 .
• Obviously, if we want to execute unit tests after the jar is generated normally in the package phase, then the unit tests should be executed in the integration-test phase. This is because the test phase occurs before the package phase.
• I opened Remove the default Maven phase bound to the metadata-copy Maven goal to simplify the use of integration tests graalvm/native-build-tools#748 to simplify the additional configuration of the metadata-copy goal.
• It is a pity that upload uninstall script and docs microsoft/Windows-Containers#602 has not been merged yet.

Before committing this PR, I'm sure that I have checked the following options:

• My code follows the code of conduct of this project.
• I have self-reviewed the commit code.
• I have (or in comment I request) added corresponding labels for the pull request.
• I have passed maven check locally : ./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e.
• I have made corresponding changes to the documentation.
• I have added corresponding unit tests for my changes.
• I have updated the Release Notes of the current development version. For more details, see Update Release Note