Creating Cloud Native Buildpacks for ShardingSphere Agent

## Feature Request

**For English only**, other languages will not be accepted.

Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot make decision by current information, we will **close it**.

Please answer these questions before submitting your issue. Thanks!

### Is your feature request related to a problem?

- See #32777 .

### Describe the feature you would like.

- In #32777 , I created two Docker Image for ShardingSphere Agent similar to https://hub.docker.com/r/apache/skywalking-java-agent . This makes it convenient for downstream to use ShardingSphere Agent without checking in the jar into git. See https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-jdbc/observability/ .
- There is a problem that not everyone likes to write an extra `Dockerfile` during the development phase, especially in the Spring Boot community. The Spring Boot community has long used Cloud Native Buildpacks to build Docker Images. Although using buildpacks requires downloading additional metadata from github.com, tools like https://github.com/dmikusa/binding-tool may be used frequently in air-gapped environments. The introduction of Buildpacks in the usage scenarios of ShardingSphere JDBC can be traced back to discussions in the Paketo community in 2022.
- I think there is a reason to create Cloud Native Buildpacks for ShardingSphere Agent, just like https://github.com/paketo-buildpacks/apache-skywalking .