Added criticality to Power BI Markdown

[ahuynhMITRE]

🗣 Description

Added the html formatting for criticality to support new field in report for future proofing and consistency to match other baselines.

💭 Motivation and context

Criticality HTML is added to support new report field and supporting automation.

Closes #689

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• All future TODOs are captured in issues, which are referenced
  in code comments.
• All relevant type-of-change labels have been added.
• I have read the CONTRIBUTING document.

✅ Pre-merge checklist

• Revert dependencies to default branches.
• Finalize version.

✅ Post-merge checklist

• Create a release.

[crutchfield]

Looks good.

[schrolla]

All 8 policy Criticality tags all conform to the format regex:
<--Policy: MS.POWERBI.\d\.\dv1; Criticality: SHOULD -->
So no misspellings or format variations, and exactly 8 matches found in the baseline.
Verified that all policies have a matching criticality and policy ID relevant to the policy scope in which they are shown.

Looks good. Only question is does this go in v1.0.0 (main) or flipper? Currently, it's targeted at main so defaulting to v1.0.0.

[ahuynhMITRE]

All 8 policy Criticality tags all conform to the format regex: <--Policy: MS.POWERBI.\d\.\dv1; Criticality: SHOULD --> So no misspellings or format variations, and exactly 8 matches found in the baseline. Verified that all policies have a matching criticality and policy ID relevant to the policy scope in which they are shown.

Looks good. Only question is does this go in v1.0.0 (main) or flipper? Currently, it's targeted at main so defaulting to v1.0.0.

fine with either since it will not affect the code at this time. Any reason not to put it in main / v1.0.0?

[schrolla]

All 8 policy Criticality tags all conform to the format regex: <--Policy: MS.POWERBI.\d\.\dv1; Criticality: SHOULD --> So no misspellings or format variations, and exactly 8 matches found in the baseline. Verified that all policies have a matching criticality and policy ID relevant to the policy scope in which they are shown.
Looks good. Only question is does this go in v1.0.0 (main) or flipper? Currently, it's targeted at main so defaulting to v1.0.0.

fine with either since it will not affect the code at this time. Any reason not to put it in main / v1.0.0?

Slightly more complex rebase/merge semantics since we already split the flipper branch. I results in a rebase cascade (rebase flipper base branch, then rebase of feature branches targetting flipper). This two level rebase can lead to issues, particularly for large PRs. And several of the rego PRs are wide ranging in the files touched. So, while I understand wanting to put it in v1.0.0 since it is more a consistency change with no visible or functional impact, I'd recommend just letting it squeak into flipper instead.

All good with me, will update the base to the flipper branch!

[ahuynhMITRE]

good to merge @nanda-katikaneni

[nanda-katikaneni]

@ahuynhMITRE - will merge this into flipper; please change the milestone for the associated issue #689 to flipper (its currently in emerald).

[schrolla]

@ahuynhMITRE - will merge this into flipper; please change the milestone for the associated issue #689 to flipper (its currently in emerald).

Noticed this as well and updated it this morning. Probably didn't refresh on your page @nanda-katikaneni if you already had it up at the time of review. Set for Flipper Sprint 1 milestone now.