Data requirement profiles

[elsaperelli]

Summary

This PR adds the meta.profile found on the templateId of an ELMRetrieve (if it exists) to the profile attribute of a data requirement.

New behavior

When the user runs dataRequirements on a measure that was authored using QI-Core, the data requirements output will now contain the profile attribute which is populated with the meta.profile, found in the templateId of the ELMRetrieve.

Code changes

• src/gaps/RetrievesFinder.ts - gets the templateId from the ELMRetrieve and adds it to the results so it can eventually get added to the data requirement.
• src/helpers/DataRequirementHelpers.ts - function addProfileToDataRequirement adds the profile to the data requirement if a templateId exists on the ELMRetrieve.
• src/types/Calculator.ts - adds optional templateId to the DataTypeQuery interface.
• test/unit/DataRequirements.test.ts - adds a unit test for addProfileToDataRequirement and fixes some typos.
• test/unit/RetrievesFinder.test.ts - adds templateId to results.

Testing guidance

• npm run check
• npm run test:integration
• Run data-requirements on a qi-core measure and a non qi-core measure and check that profile exists on the data requirements output and is correct. Question: do we want this to be populated for non qi-core measures as well? That is the current functionality.

[github-actions[bot]]

Coverage report

St.:grey_question:	Category	Percentage	Covered / Total
🟢	Statements	86.35% (+0.02% 🔼)	2366/2740
🟡	Branches	73.64%	2190/2974
🟢	Functions	88.89%	424/477
🟢	Lines	86.69% (+0.02% 🔼)	2286/2637

Test suite run success

448 tests passing in 31 suites.

Report generated by 🧪jest coverage report action from c4607aae351cf9b0eef3dcc9d99ea9083fcf0274