RANGER-4076: Support Java 17 for build and runtime

[RakeshGuptaDev]

What changes were proposed in this pull request?

Support for Java 17 has been added in both build and runtime environments, along with support for Java 8 and 11 in both environments.

How was this patch tested?

This patch has been successfully tested and verified on Java versions 8, 11, and 17. The verification process involved both manual testing and a Docker-based setup. We can now build and run the patch on the same JDK version.

Maven Build Verification

JDK 8:
mvn clean compile package install

JDK 11:
mvn clean compile package install

JDK 17:
mvn clean compile package install -Pranger-all-modules-jdk17

Validated policy enforcement for below scenario :

Scenario 1: JDK 8 Build and Runtime
Successfully validated Usersync, Tagsync, and Policy Enforcement (including policy conditions) for HDFS, HBase, and Hive services using Ranger with JDK 8 for both build and runtime environments.

Scenario 2: JDK 8 Build and JDK 17 Runtime
Successfully validated Usersync, Tagsync, and Policy Enforcement (including policy conditions) for HDFS and HBase services using Ranger with JDK 8 for the build and JDK 17 for the runtime environment.

Scenario 3: JDK 17 Build and Runtime
Successfully validated Usersync, Tagsync, and Policy Enforcement (including policy conditions) for HDFS and HBase services using Ranger with JDK 17 for both build and runtime environments.

[mneethiraj]

Good work @RakeshGuptaDev! One concern is that many Ranger plugins need to run in JDK version prior to 17 (JDK8 or JDK 11 or JDK15) - like HDFS, Hive, HBase. This wouldn't allow us to switch to Graal script engine, as it is only available in JDK17 onwards (https://www.graalvm.org/jdk17/docs/).

One option to consider building Ranger libraries used by plugins (agents-common, agents-audit, agents-cred, all plugins) with JDK8 and servers (admin, usersync, tagsync, KMS) with JDK17.