Azure-docs: [meta] Strip BOM characters from Markdown files

[nschonni]

Markdown files encoded with a BOM do not render the markdown files correctly on GitHub and the PR Bots can't read the front matter. I previously opened https://github.com/MicrosoftDocs/azure-docs/pull/10954 to fix this, and it includes instructions for a bulk cleanup.
/cc @ktoliver @SyntaxC4

[nschonni]

When I ran the script today there are 848 files https://github.com/nschonni/azure-docs/commit/e3566862508b4fa0148bece293a69bd3d3d24c71

[Mike-Ubezzi-MSFT]

@amanarneja In terms of Community workflow, not sure how to redirect this within Watchtower. @nschonni Can this be assigned to you?

[nschonni]

@Mike-Ubezzi-MSFT I don't think so since my previous PR was closed due to the size. It's probably better done internally in sizes that is reviewable for your group.

[amanarneja]

@SyntaxC4 / @ShevaDas - Can you take a look at this ?

[ghost]

Megan is working on validation in our publishing build system for this. This issue should probably be kept open until that functionality is delivered. cc @meganbradley

[meganbradley]

Thanks @tysonn .

@nschonni BOM characters are in scope for our next round of validation work.

[shirgoldbird]

Can this be closed out? It looks like #1759 is closed.

[nschonni]

@shirgoldbird that PR doesn't seem related to this issue

[meganbradley]

@nschonni @shirgoldbird Validation for BOM characters is in scope for the Markdown validation epic, which we'll start after metadata validation is complete. I'm not sure when the BOM validation will be live - hopefully by the end of June, but I can't promise that.