`GRAALVM_HOME` should not be set after switching GraalVM CE or Oracle GraalVM

[linghengqian]

• I noticed that Not setting GRAALVM_HOME #1 requires setting GRAALVM_HOME after switching GraalVM CE or Oracle GraalVM. And there is this logic at https://github.com/version-fox/vfox-java/blob/main/hooks/env_keys.lua#L21 .
• From my point of view, this is unreasonable behavior, because GRAALVM_HOME is usually not consistent with JAVA_HOME. In the GraalVM community, developers often use GRAALVM_HOME to bypass Gradle's restrictions on JDK runtime to compile GraalVM Native Image, because the Gradle version used by the GraalVM community is usually very old. Refer to The build of the task :native-gradle-plugin:functionalTest in the master branch failed in Oracle GraalVM For JDK 23.ea.13 graalvm/native-build-tools#606 (comment) .
• Early investigation came from Add runtimeArgs support to native-maven-plugin graalvm/native-build-tools#734 .