feat(build): support jdk8 spark lineage

[david-leifker]

The Spring 6 changes along with the gradle build configuration introduced a situation where all modules were mostly building with the newer jdk17. This was a bug since we still want to rely on jdk11 for modules like the datahub-client. This restores datahub-client to jdk11 as well as support jdk8 for the spark lineage plugin.

This was accomplished with some dynamic logic at the beginning of the main gradle file to determine if there is a Spring 6 or Spring Boot 3 dependency. If so, then jdk17 is the only supported option.

For modules supporting the datahub-client, such as metadata-models, we ensure that the target class version is used with the addition of the jdk8 spark test. If that ci test fails to compile then we've broken an expected jdk constraint.

As a side-effect, instances of source code which moved to newer language specifications was discovered. These instances were downgraded to jdk8 compatible code (only a few items).

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[RyanHolstien]

Sad to see some of the nice JDK17 syntax improvements go :'( but lgtm