Convert baseline markdown files to text and HTML

[james-garriss]

🗣 Description

This PR converts the existing baseline files that are in Markdown to both HTML and text format. It saves them to the baselines folder and then makes that folder available as an artifact.

💭 Motivation and context

Closes: #1376

🧪 Testing

Wrote and tested original workflow in an alternate repository.
Once workflow was working, moved to SG repo and modified accordingly.
Verified expected results were found in the artifact.

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• PR targets the correct parent branch (e.g., main or release-name) for merge.
• Changes are limited to a single goal - eschew scope creep!
• Changes are sized such that they do not touch excessive number of files.
• These code changes follow the ScubaGear [content style guide]
• Related issues these changes resolve are linked preferably via [closing keywords]
• All relevant type-of-change labels added.
• All relevant project fields are set.
• All automated checks (e.g., linting, static analysis, unit/smoke tests) passed.

✅ Pre-merge checklist

• PR passed smoke test check.
• Feature branch has been rebased against changes from parent branch, as needed
• Resolved all merge conflicts on branch
• Notified merge coordinator that PR is ready for merge via comment mention

✅ Post-merge checklist

• Feature branch deleted after merge to clean up repository.
• Verified that all checks pass on parent branch (e.g., main or release-name) after merge.

[buidav]

Looks good.
Wish there was a way to for loop this somehow but doing that in this workflow would be adding unnecessary abstraction.
Since, we don't change the baseline document names/locations often.

[james-garriss]

I don't disagree with the idea of a loop, @buidav , but given that we don't really understand what Drupal needs at this point, I was reluctant to spend more time on this task. I will put this on my personal backlog. If/when we get clarification, I will look at moving this into code (.ps1 function), where we can use a loop and add unit testing.

[mitchelbaker-cisa]

Verified html/text files from output and looks good.

[james-garriss]

@nanda-katikaneni