Introduce MeasureEnvironment: consolidate endpoint params, resolve at construction

[JPercival]

Summary

Consolidates contentEndpoint, terminologyEndpoint, dataEndpoint, and additionalData into a single MeasureEnvironment record, then moves resolution to the right place in the pipeline.

MeasureEnvironment record

public record MeasureEnvironment(
    @Nullable IBaseResource contentEndpoint,
    @Nullable IBaseResource terminologyEndpoint,
    @Nullable IBaseResource dataEndpoint,
    @Nullable IBaseBundle additionalData) {

    public static final MeasureEnvironment EMPTY = ...;
    public IRepository resolve(IRepository base) { ... }
}

Version-agnostic (IBaseResource/IBaseBundle) so it lives cleanly in measure/common without importing version-specific FHIR types. MeasureEnvironment.resolve() is the single place that composes the repository: endpoint proxy if all three endpoints are set, then additional-data federation on top.

Environment resolved at construction, not at evaluation

Per the operation pipeline (Architecture.md):

HAPI Provider → Environment Config → Runtime → Denormalization

Environment config must happen before the runtime, not inside it. Previously contentEndpoint, terminologyEndpoint, dataEndpoint, additionalData flowed through every layer as four separate parameters and were resolved deep inside R4MultiMeasureService.evaluateToListOfList().

After this change:

1. HAPI providers build MeasureEnvironment from @OperationParam inputs
2. Pass it to factory.create(requestDetails, environment)
3. Factory calls environment.resolve(repositoryFactory.create(requestDetails))
4. Service is constructed with the fully-configured IRepository
5. evaluate() methods take only domain parameters — no MeasureEnvironment

MeasureEnvironment is completely absent from R4MeasureEvaluatorSingle, R4MeasureEvaluatorMultiple, Dstu3MeasureEvaluatorSingle, and both service implementations.

resolveRepository lifecycle

Environment resolution builds up the repo in two steps, now made explicit:

• Endpoint proxy: Repositories.proxy() when all three endpoints are configured
• Additional data federation: FederatedRepository overlay when additionalData is non-null

Both steps happen once, at construction. The CQL engine receives the already-federated resolvedRepo (not the bundle again separately).

Test plan

• All R4 measure tests pass
• spotlessCheck passes

🤖 Generated with Claude Code

[github-actions]

Formatting check succeeded!

[sonarqubecloud]

Quality Gate failed

Failed conditions
74.1% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud