Enhance test coverage and update dependencies for development

[mercyblitz]

This pull request introduces significant improvements to CI workflows and enhances unit test coverage across the codebase. The main changes include automating branch merges from main to dev and release, expanding and strengthening test cases for collections and converters, enforcing versioning standards in the Maven publishing workflow, and adding a new release automation step. There are also minor improvements to builder defaults and test coverage for classloading utilities.

CI/CD Workflow Enhancements:

• Added a new GitHub Actions workflow (merge-main-to-branches.yml) that automatically merges the main branch into dev and release branches on every push to main, reducing manual maintenance and ensuring branch consistency.
• Improved the Maven publishing workflow (maven-publish.yml) by:
  • Enforcing a strict semantic versioning format for the revision input and validating it before proceeding. [1] [2]
  • Adding a new release job that creates a git tag and GitHub release, bumps the patch version in pom.xml, and pushes the updated version for continued development.

Test Coverage Improvements:

• Greatly expanded unit tests for collection utilities:
  • AbstractDequeTest: Added tests for getFirst, getLast, removeLastOccurrence, descendingIterator, size checks, and more, improving coverage and robustness. [1] [2] [3] [4]
  • ListsTest, SetsTest, MapsTest: Added immutability tests to ensure returned collections are unmodifiable. [1] [2] [3] [4] [5] [6]
• Added a new test class for StringToByteConverter, including negative test cases for conversion failures.
• Improved converter and classloading tests:
  • Added hash code and priority tests to AbstractConverterTest. [1] [2]
  • Added tests for ArtifactDetector with and without JDK libraries.
  • Added a test for setPriority in AbstractURLClassPathHandleTest.

Other Improvements:

• Set a default value for the level field in the Deprecation.Builder class, improving builder usability.

These changes collectively improve the reliability, maintainability, and automation of the project.

References:
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]

[codecov]

Codecov Report

❌ Patch coverage is 98.14815% with 2 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
.../src/main/java/io/microsphere/collection/Sets.java	94.44%	2 Missing ⚠️

Files with missing lines	Coverage Δ	Complexity Δ
...src/main/java/io/microsphere/collection/Lists.java	97.67% <100.00%> (+40.91%)	38.00 <35.00> (+24.00)
.../src/main/java/io/microsphere/collection/Maps.java	97.67% <100.00%> (+43.62%)	38.00 <35.00> (+24.00)
...src/main/java/io/microsphere/lang/Deprecation.java	100.00% <ø> (ø)	23.00 <0.00> (ø)
.../src/main/java/io/microsphere/collection/Sets.java	94.18% <94.44%> (+46.88%)	37.00 <35.00> (+24.00)

... and 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sonarqubecloud]

Quality Gate failed

Failed conditions
B Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE