Add 'reports' module and Kover plugin

[kpavlov]

This pull request includes several changes to integrate Kotlin enhancements, add coverage reporting, and update the build configuration for the project. The most important changes are listed below:

Build and CI Configuration:

• Updated the CI workflow name from "Java CI with Maven" to "Kotlin CI with Maven" in .github/workflows/maven.yml.
• Added a step to run codacy-coverage-reporter in the CI workflow.
• Enabled parallel build with 12 threads in .mvn/maven.config.

Maven and Reporting:

• Added the reports module to the pom.xml file to include coverage reporting.
• Integrated the kover-maven-plugin for Kotlin code coverage reporting in pom.xml. [1] [2]

Documentation:

• Updated the badge in README.md to reflect the new CI workflow name and added a badge for Codacy coverage.

New Files:

• Added reports/pom.xml to configure the kover-maven-plugin for generating and verifying coverage reports.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for 71edca01	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (71edca0)	Report Missing	Report Missing	Report Missing
Head commit (5d1390e)	23	5	21.74%

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 (#13)	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}

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩