feat: add infinispan java 11 module

[iProdigy]

Closes #123

Separate module due to Java 11 requirement

[sonatype-lift]

🛠 Lift Auto-fix

Some of the Lift findings in this PR can be automatically fixed. You can download and apply these changes in your local project directory of your branch to review the suggestions before committing.¹

# Download the patch
curl https://lift.sonatype.com/api/patch/github.com/Xanthic/cache-api/132.diff -o lift-autofixes.diff

# Apply the patch with git
git apply lift-autofixes.diff

# Review the changes
git diff

Want it all in a single command? Open a terminal in your project's directory and copy and paste the following command:

curl https://lift.sonatype.com/api/patch/github.com/Xanthic/cache-api/132.diff | git apply

Once you're satisfied, commit and push your changes in your project.

Footnotes

1. You can preview the patch by opening the patch URL in the browser. ↩

[PhilippHeuer]

What do you think about these names?

• cache-provider-infinispan
• cache-provider-infinispan-java11

This is easier to maintain as most infinispan releases won't change the java version requirement.
The suffix -java11 seems to be used a lot in such cases, see https://central.sonatype.com/search?smo=true&q=-java11.

[iProdigy]

Good idea - is Infinispan11Delegate too ambiguous (jdk 11 or lib v11)?

[PhilippHeuer]

We could also differentiate using the package:

• io.github.xanthic.cache.provider.infinispan
• io.github.xanthic.cache.provider.infinispanjdk11

This way we can keep the same names / copy all files between the two packages. (at least until a breaking change affects the code)

If we change the name, i would prefer InfinispanJava11Delegate to ensure users don't think it's infinispan v11.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
65.9% Duplication