Update jUnit to 5.11

[vitalijr2]

• Remove tokenAuth from Maven publishing plugin's configuration: it's obsolete.

• Remove tokenAuth from Maven publishing plugin's configuration: it's obsolete.

• Optimize import. Skip tests when it runs a demo

• Bump org.hamcrest:hamcrest from 2.2 to 3.0

Bumps org.hamcrest:hamcrest from 2.2 to 3.0.

• Release notes
• Changelog
• Commits

---

updated-dependencies:

• dependency-name: org.hamcrest:hamcrest dependency-type: direct:development update-type: version-update:semver-major ...

• Bump junit-jupiter.version from 5.10.3 to 5.11.0 and org.junit.platform:junit-platform-commons from 1.10.3 to 1.11.0

---

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00% (target: -1.00%)	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (626ec28)	30	30	100.00%
Head commit (1733665)	60 (+30)	60 (+30)	100.00% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#24)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.