Add Release Profile for distribution/proxy-native

[linghengqian]

For #21347.

Changes proposed in this pull request:

• Add Release Profile for distribution/proxy-native.
• Update GraalVM Native Build Tools to 0.9.16.
• Add the corresponding LICENSE.
• Fixes the wrong Docker Base Image in the Dockerfile, because the current GraalVM Native Build Tools is still using dynamic linking instead of static linking, which requires more system library support.
• Switched CI from https://github.com/graalvm/graalvm-ce-builds to https://github.com/graalvm/graalvm-ce-dev-builds for faster resolution of earlier issues. This is mainly because a series of fixes related to the file system for GraalVM Native Image is currently only in the dev build of GraalVM, and we need to verify it earlier. Issues like Cannot resolve FileSystem root resource in Native Image oracle/graal#5020 and Native Image FileSystem is trailing slash sensitive oracle/graal#5080 actually solve a bunch of problems around being a directory instead of a file .

---

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 : mvn clean install -B -T2C -DskipTests -Dmaven.javadoc.skip=true -e.
• I have made corresponding changes to the documentation.
• I have added corresponding unit tests for my changes.

[linghengqian]

For this PR, if you need a binary package of release distribution/proxy-native, you need to execute ./mvnw -am -pl distribution/proxy-native -B -DskipTests -Dmaven.javadoc.skip=true -Dcheckstyle.skip=true - Dspotless.apply.skip=true -Pnative,release clean package. This requires both GraalVM CE for JDK 17 and the native-image component of GraalVM installed on the device on which this command is executed. In which document should I state this?

[linghengqian]

@strongduanmu I just want to make sure, does such a release note exist? 🤣

[strongduanmu]

@linghengqian I think we can add this requirement in ShardingSphere release document——https://shardingsphere.apache.org/community/cn/involved/release/shardingsphere/#3-%E5%8F%91%E5%B8%83-docker.

[linghengqian]

• I looked at the Dockerfile and release process of distribution/proxy and found that all the raw materials used to build the Docker Image are extracted from the .tar.gz file generated by the release profile.

• Is this an unwritten rule, or is it possible to make a Docker Image without making an intermediate .tar.gz? I'm not quite sure if .tar.gz is only needed for distributing binaries.

• If this provision exists, I will fix the Dockerfile of distribution/proxy-native when opening a new PR.

[linghengqian]

• Do I have to copy and paste so much LICENSE content? Can I directly refer to the path where the distribution/proxy's LICENSE is located for packaging? 👀