Retain trigger code OIDs in refined eICR output

[robertmitchellv]

Action Requested

During the eICR validation process it was uncovered that we must retain the trigger code OIDs that are added to the various sections within the <structuredBody> via templateId tags in order for messages to be valid. Removing them results in a fatal error and at least one of these OIDs needs to be included in an eICR.

It makes sense that even if we're going to remove sections based on the sections_to_include that we retain these OIDs via templateId since there will still be a level of provenance as well as preventing fatal errors in XML validation.

AS a $USER, I want to retain OID trigger code values SO THAT fatal errors are not introduced to the refining process

Acceptance Criteria

When can we call this done?

GIVEN an eICR with trigger code OIDs in its sections WHEN those sections are included to be removed THEN the OIDs are retained in the templateId tag in the empty section

Testing

Tests will need to be added

Background & Context

This is important to users because we want our process to not introduce any errors or warnings to messages from our refining process.