Update README to inform those with java version managers

[Obsiye]

1. Upgrade dependency-check-maven
2. Update README to describe the effect of maven with a java version manager like jenv. Use jenv enable-plugin maven in order for maven to use the correct java version

Why?

I had initial difficulty during the setup phase. The issue was that the repo uses java 8 and so I had to use a java version manager for switching versions. Maven was unable to update its java_home location until I enabled the maven plugin for jenv.

EDIT:

Reply to Giuseppe: Thank you, i'll try to make the changes on Friday during my L&D

[your]

@Obsiye thank you for raising this PR! 🙌

Unfortunately, It looks like there might be a little bit more work involved before we can get this merged... 😢

1. The Travis build is not running as travis-ci.org has been discontinued and it probably makes sense to quickly replace it with a Github action to run the maven build
2. We need to bump a few more dependencies (or add them to the OWASP suppression list in the root folder - if deemed false positives).

If you need my help, happy to contribute to this branch.

One or more dependencies were identified with vulnerabilities that have a CVSS score greater than or equal to '8.0':

esapi-2.0.1.jar: CVE-2022-23457(9.8)
logback-core-1.1.11.jar: CVE-2021-42550(6.6), CVE-2017-5929(9.8)
spring-core-4.3.16.RELEASE.jar: CVE-2022-22965(9.8)
spring-security-core-4.2.3.RELEASE.jar: CVE-2022-22978(9.8), CVE-2021-22112(8.8)
spring-web-4.3.16.RELEASE.jar: CVE-2022-22965(9.8), CVE-2016-1000027(9.8)
velocity-1.7.jar: CVE-2020-13936(8.8)