FI-582: Data Absent Reason tests

[Jammjammjamm]

This branch adds tests for data absent reasons. It ties into fetch_all_bundle_resources and validate_read_reply to search each retrieved resource for the data absent reason extension and the data absent reason code. The TestingInstance tracks whether each of these have been found, and then the actual data absent reason sequence just checks the values on TestingInstance. As part of this branch I also added a way to include static files with the US Core generation.

Submitter:

• This pull request describes why these changes were made
• Internal ticket for this PR: https://oncprojectracking.healthit.gov/support/browse/FI-582
• Internal ticket links to this PR
• Internal ticket is properly labeled (Community/Program)
• Internal ticket has a justification for its Community/Program label
• Code diff has been reviewed for extraneous/missing code
• Tests are included and test edge cases
• Tests/code quality metrics have been run locally and pass

Reviewer 1:

Name:

• Code is maintainable and reusable, reuses existing code and infrastructure
  where appropriate, and accomplishes the task's purpose
• The tests appropriately test the new code, including edge cases
• You have tried to break the code

Reviewer 2:

Name:

• Code is maintainable and reusable, reuses existing code and infrastructure
  where appropriate, and accomplishes the task's purpose
• The tests appropriately test the new code, including edge cases
• You have tried to break the code

[ghost]

Is there a reason why you don't do check_for_data_absent_reasons for multiple-or tests?

[Jammjammjamm]

That's just an oversight, thanks for bringing it up.

[Jammjammjamm]

@czh-orz The multiple or tests now check for data absent reasons.

[arscan]

Looks good. Our data set generator doesn't support the CodeSystem one yet, but I think it should.