Service Loading Example

[zack-rma]

Description

Example implementation of service loader for solver-like test classes.

Motivation and Context

Provides examples to resolve #214

Types of changes

Yes/No	Pull Request Type	Description
	Bug fix	non-breaking change which fixes an issue
	New feature	non-breaking change which adds functionality
	Breaking change	fix or feature that would cause existing functionality to change
	Documentation change	non-breaking change which modifies or updates documentation
	New tests	new unit tests, test scenarios, or test case documentation
	Triggers regression testing	change affects downstream modules and will require regression testing
Y	Other	Example implementation

How Has This Been Tested?

Includes unit test.

Notes for Reviewers

Please consider the following when reviewing this PR:

• Correctness: Does the code do what it claims? Are edge cases handled appropriately?
• Clarity: Is the code readable, maintainable and aligned with SOLID design principles?
• Impact: Will this change affect other parts of the system? Any potential regressions?
• Testing: Are the test cases sufficient and appropriate? Are there gaps in coverage?
• Documentation: Does this require updates to code comments, README, or other docs?

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)
11.7% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud