Add expected: blocks to Measles Low Transmission test YAML

[lambdabaa]

Summary

• Adds an expected: block to each of the seven existing patient documents in input/tests/plandefinition/IMMZD2DTMeaslesLowTransmissionLogic/IMMZD2DTMeaslesLowTransmissionLogic.yaml, encoding the expected boolean and guidance-string outputs of the Logic library per patient.
• Zero behaviour change to the IG Publisher build, makeExample.js, or the Karate .feature generation — purely additive YAML keys.
• Concrete companion to RFC issue RFC: machine-readable expected: blocks in test YAMLs #136.

Schema

Blocks follow the convention proposed in #136:

expected:
  row: IMMZ.D2.DT.Measles.LowTransmission.R1
  defines:
    "Client is not due for MCV1 Case 1": true
    "Client is not due for MCV1": true
    "Guidance":
      equals: "Should not vaccinate client with MCV1 as client's age is less than 12 months.\nCheck for any vaccines due and inform the caregiver of when to come back for MCV1."

Identifiers correspond to the published CQL define "<name>": declarations in input/cql/IMMZD2DTMeaslesLowTransmissionLogic.cql.

Provenance of the expected values

Each block was derived from existing artefacts already in this repository:

• the ### … natural-language outcome lines already present at the top of each patient document, and
• the Test Validation case-expression in input/cql/IMMZD2DTMeaslesLowTransmissionLogic.cql.

The blocks were independently verified by running the published Logic library against the existing patient bundles using cqframework/cql-execution at submodule HEAD (b16245f); all 7 cases produce values that match the encoded expected: blocks.

Compatibility

• tools/node/makeExample.js accesses YAML keys by name (id, birth, patient, immunization, contraindication, medicationrequest) and ignores others.
• tools/node/processDAK.js --existing re-emits arbitrary parsed keys, so the block survives regeneration from the L2 Excel source.
• No change to the IG Publisher build, qa.html, or input/testing/features/plandefinition/<X>/<X>.feature.

Test plan

• WHO maintainer review of the schema (defer to RFC RFC: machine-readable expected: blocks in test YAMLs #136 for the cross-cutting convention discussion).
• Sanity-check by running tools/node/makeExample.js against the patched YAML; per-resource JSON output should be identical to the unpatched run.
• Optional: run the patched YAML through the IG Publisher locally and confirm qa.html is unchanged.