RANGER-4076: Support Java 17 for build and runtime

[pradeepagrawal8184]

What changes were proposed in this pull request?

Support jdk17 build in Ranger. This change shall discontinue build support on jdk8/11

How was this patch tested?

Manual install, start and crud operations on the policy, group, users, service etc.

[kumaab]

Thanks @pradeepagrawal8184 for this patch, I think it is best to update the CI/CD build in this PR by removing builds for JDK8 and JDK11 and adding support for JDK17.

The jobs build-8 and build-11 can be removed from https://github.com/apache/ranger/blob/master/.github/workflows/ci.yml and a similar one for build-17 can be added, the docker builds don't require changes.

[pradeepagrawal8184]

Current ranger master branch shipped jars vs jar shipped with this branch changes.
ranger-master-jars.txt
ranger-4076-jars.txt

[ramackri]

Hi @pradeepagrawal8184,
As part of the JDK 17 upgrade, are we planning to migrate from Spring 5.x to Spring 6.x as well, or will the Spring upgrade be handled separately after this PR is merged?
We’ve observed that several CVE issues are addressed in Spring 6.x, so wanted to understand the plan.
cc >> @mneethiraj

[pradeepagrawal8184]

Hi @pradeepagrawal8184, As part of the JDK 17 upgrade, are we planning to migrate from Spring 5.x to Spring 6.x as well, or will the Spring upgrade be handled separately after this PR is merged? We’ve observed that several CVE issues are addressed in Spring 6.x, so wanted to understand the plan. cc >> @mneethiraj

@ramackri : Spring upgrade can be handled separately. We can discuss that in the spring upgrade ticket after this PR merge and decide.

[kumaab]

I've reviewed the changes partially (since this is a big patch), some JWT related functionalities recently added seems to have been removed, please rebase and take a look. thanks.

[vyommani]

Overall LGTM.

This is a significant and well-executed upgrade to Java 17. Thanks for handling the pom updates, Docker changes, Nashorn removal, Jersey migration, and test fixes across the board.

Minor suggestions:

Consider removing vim from the Docker images if not strictly required.
Ensure the CI workflow now only runs on JDK 17.

Great work @pradeepagrawal8184!