Update Gradle and dependencies

[theimpulson]

• I carefully read the contribution guidelines and agree to them.
• I have tested the API against NewPipe.
• I agree to create a pull request for NewPipe as soon as possible to make it compatible with the changed API.

[theimpulson]

We cannot update checkstyle as latest version seems to require JDK 17 and above while we are enforcing JDK 11 bytecode.

[theimpulson]

We cannot update checkstyle as latest version seems to require JDK 17 and above while we are enforcing JDK 11 bytecode.

I figured this out with https://docs.gradle.org/current/userguide/toolchains.html#toolchains_for_tasks

[TobiGr]

We should apply the use of the newer JDK to all files:

NewPipeExtractor/build.gradle.kts

Line 19 in 8972df0

languageVersion.set(JavaLanguageVersion.of(11))

https://github.com/TeamNewPipe/NewPipeExtractor/blob/8972df0a062fc98b623d8e286d83b8aea4343747/jitpack.yml

I think the policy was to keep the compile JDK low and to not use new language features to support the lowest LTS version, which is now 17 as 11 went EOL this year. Should we stick to that? @Stypox @FireMasterK

[theimpulson]

We should apply the use of the newer JDK to all files:

NewPipeExtractor/build.gradle.kts

Line 19 in 8972df0

languageVersion.set(JavaLanguageVersion.of(11))

https://github.com/TeamNewPipe/NewPipeExtractor/blob/8972df0a062fc98b623d8e286d83b8aea4343747/jitpack.yml

I think the policy was to keep the compile JDK low and to not use new language features to support the lowest LTS version, which is now 17 as 11 went EOL this year. Should we stick to that? @Stypox @FireMasterK

Can we go ahead with this PR for now and do this discussion separately to unblock it as bumping JDK version isn't the aim for this PR?

[Stypox]

I think the policy was to keep the compile JDK low and to not use new language features to support the lowest LTS version, which is now 17 as 11 went EOL this year. Should we stick to that?

Yeah I guess it makes sense to switch to Java 17 now