Conflicting Java Version Requirements

[frederikb]

Describe the bug
The pom.xmls specify Java 11 as the source/target/release version, while the README indicates Java 17+ is required in the “Building” section.

To Reproduce

cluecumber/pom.xml

Lines 25 to 27 in 05b9682

	<maven.compiler.source>11</maven.compiler.source>
	<maven.compiler.target>11</maven.compiler.target>
	<maven.compiler.release>11</maven.compiler.release>

cluecumber/engine/pom.xml

Line 30 in 05b9682

<maven.compiler.release>11</maven.compiler.release>

cluecumber/core/pom.xml

Line 42 in 05b9682

<maven.compiler.release>11</maven.compiler.release>

cluecumber/maven/pom.xml

Line 42 in 05b9682

<maven.compiler.release>11</maven.compiler.release>

cluecumber/README.md

Line 51 in 05b9682

Cluecumber requires Java >= 17 and Maven >= 3.6.3.

Expected behavior
Alignment of Java versions. Probably adjusting the versions in the pom.xml to 17. This would however mandate a breaking change.