Refactor of the way Lambda job classes are identified

Fixes #2370.

Changes proposed in this pull request:

Refactor of the way Lambda job classes are identified. Also fixes #2224 .
More discussion on GraalVM CE For JDK22 is at https://github.com/oracle/graal/pull/7775 .
More discussion on OpenJDK 20 can be found at https://forums.oracle.com/ords/apexds/post/why-did-the-class-name-of-the-lambda-class-change-starting-7639 .
Starting from this PR,
- For the ElasticJob Lambda job class on JDK21-JDK23, the identifier of org.apache.shardingsphere.elasticjob.kernel.internal.setup.DefaultJobClassNameProviderTest$$Lambda/0x00007f28230abcc0 will be changed from org.apache.shardingsphere.elasticjob.kernel.internal.setup.DefaultJobClassNameProviderTest$$Lambda/0x00007f28230abcc0 to org.apache.shardingsphere.elasticjob.kernel.internal.setup.DefaultJobClassNameProviderTest$$Lambda.
- For ElasticJob Lambda job classes on JDK8-JDK20, the identifier of org.apache.shardingsphere.elasticjob.kernel.internal.setup.DefaultJobClassNameProviderTest$$Lambda$372/0x00007f98c00accb8 will change from org.apache.shardingsphere.elasticjob.kernel.internal.setup.DefaultJobClassNameProviderTest$$Lambda$ to org.apache.shardingsphere.elasticjob.kernel.internal.setup.DefaultJobClassNameProviderTest$$Lambda.
Update the Release Notes of my personal PR according to the requirements of https://shardingsphere.apache.org/community/cn/involved/contribute/contributor/ .
Bump the Spring Boot version used by nativeTest in GraalVM Native Image to 3.3.5.

apache / shardingsphere-elasticjob