Require JDK 17 rather than JDK 11

[Stephan202]

❗ This PR is on top of #604. ❗ This now targets master.

This PR is spun off from #198. The idea is that it is merged first; the scope of #198 is then reduced to text block support for CompilationTestHelper and BugCheckerRefactoringTestHelper.

❗ A lot of discussion in this PR was around use of Jabel. This turned out to cause flaky GitHub Actions builds, so eventually we decided to simply raise the project's baseline to JDK 17. This was the now obsolete suggested commit message:

Use Jabel to enable use of JDK >11 constructs while still targeting JDK 11 (#603)

The build now effectively requires JDK 17, though continued compatibility with
JDK 11 is validated by means of Surefire tests that use Maven Toolchains 
support to run JDK 11. 

Through Jabel, only a subset of new language features can be made compatible
with earlier versions of Java, so not all JDK 17 functionality can be used yet.
Similarly, APIs introduced after JDK 11 can also not be used yet.

Constructs that can now be used include text blocks, switch expressions and 
`instanceof` pattern matching. The code has been updated to make use of these
new constructs.

While there, make sure that the `sonar` Maven profile is picked up during
SonarCloud analysis.

See:
- https://github.com/bsideup/jabel
- https://maven.apache.org/guides/mini/guide-using-toolchains.html

New suggested commit message:

Require JDK 17 rather than JDK 11 (#603)

By raising this baseline the project can now use Java 17 language features such
as text blocks, switch expressions and `instanceof` pattern matching. The code
has been updated to make use of these constructs.

Note that the project can still be used by builds that target an older version
of Java, as long as those builds are executed using JDK 17+.

[Stephan202]

Open points (will circle back to this PR over the coming days):

1. A closer look at the JDK 20 compilation error; likely something due to Jabel.
2. Addressing the SonarCloud-reported issues.
3. Reviewing whether the Pitest-reported missing coverage is accurate/matches coverage on the target branch.

[Stephan202]

I filed bsideup/jabel#177 for the JDK 20 build error. (We should also update the GitHub Actions workflow to use the latest JDK 20 release, but I'll open a separate PR for that.)

[Stephan202]

but I'll open a separate PR for that.

Filed #604.

[Stephan202]

Rebased PR on top of #604.

[Stephan202]

Updated the branch. The SonarCloud alerts have been resolved. I verified that all surviving mutations reported by Pitest are also present on the target branch; resolving those is out of scope.

The only open point is the Jabel JDK 20 incompatibility; let's wait for a few days to see whether we can get a new release for that. Alternatively we can temporarily disable the JDK 20 build.

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues

Measures
0 Security Hotspots
92.8% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[Stephan202]

I rebased and added two more small commits, introducing a few more text blocks (and thus resolving some more SonarCloud violations).

I'll merge once built, so that I can start rebasing other PRs. (@rickie I realize that this skips a review opportunity; happy to open follow-up PRs.)

[Stephan202]

We don't use .formatted elsewhere, but i.c.w. text blocks it makes sense. Let's review whether we want to switch all String.format usages.

[github-actions]

• Surviving mutants in this change: 11
• Killed mutants in this change: 172

class	surviving	killed
🧟tech.picnic.errorprone.utils.AnnotationAttributeMatcher	3	0
🧟tech.picnic.errorprone.experimental.bugpatterns.MethodReferenceUsage	2	17
🧟tech.picnic.errorprone.bugpatterns.SpringMvcAnnotation	1	9
🧟tech.picnic.errorprone.bugpatterns.PrimitiveComparison	1	13
🧟tech.picnic.errorprone.refaster.runner.Refaster	1	2
🧟tech.picnic.errorprone.guidelines.bugpatterns.RefasterAnyOfUsage	1	8
🧟tech.picnic.errorprone.bugpatterns.CanonicalAnnotationSyntax	1	4
🧟tech.picnic.errorprone.bugpatterns.LexicographicalAnnotationAttributeListing$1	1	1
🎉tech.picnic.errorprone.bugpatterns.StaticImport	0	4
🎉tech.picnic.errorprone.documentation.BugPatternTestExtractor$BugPatternTestCollector	0	8
🎉tech.picnic.errorprone.refaster.test.RefasterRuleCollection	0	4
🎉tech.picnic.errorprone.bugpatterns.RedundantStringConversion	0	9
🎉tech.picnic.errorprone.bugpatterns.LexicographicalAnnotationAttributeListing	0	4
🎉tech.picnic.errorprone.bugpatterns.JUnitValueSource	0	8
🎉tech.picnic.errorprone.bugpatterns.NonStaticImport	0	2
🎉tech.picnic.errorprone.bugpatterns.DirectReturn	0	9
🎉tech.picnic.errorprone.guidelines.bugpatterns.UnqualifiedSuggestedFixImport	0	4
🎉tech.picnic.errorprone.bugpatterns.FormatStringConcatenation$ReplacementArgumentsConstructor	0	2
🎉tech.picnic.errorprone.refaster.matchers.ThrowsCheckedException	0	8
🎉tech.picnic.errorprone.bugpatterns.AmbiguousJsonCreator	0	2
🎉tech.picnic.errorprone.utils.MoreJUnitMatchers	0	4
🎉tech.picnic.errorprone.bugpatterns.CanonicalClassNameUsage	0	4
🎉tech.picnic.errorprone.bugpatterns.MockitoMockClassReference	0	8
🎉tech.picnic.errorprone.refaster.test.RefasterRuleCollection$UnexpectedMatchReporter	0	3
🎉tech.picnic.errorprone.bugpatterns.IsInstanceLambdaUsage	0	4
🎉tech.picnic.errorprone.refaster.matchers.IsEmpty	0	2
🎉tech.picnic.errorprone.refaster.matchers.IsLikelyTrivialComputation	0	29

Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.