Add script that validates all files in the repo contain ASCII-only bytes and no UTF-8 BOM.

[ahsonkhan]

Part of #1201

As a follow up to #1198 which fixes any non-ASCII related issues we have, I wanted to enable a CI-validating leg for this so that we stay green.

[ahsonkhan]

FYI, @vhvb1989

[ahsonkhan]

Blocked on Azure/azure-sdk-tools#946 and #1198

[ahsonkhan]

Files found with non-ASCII characters: 8

6 are being fixed by #1198 (although there are a couple of duplicates)
1 is being fixed by Azure/azure-sdk-tools#946
1 is about the build directory

• Do not save the generated Cobertura XML file with a UTF-8 BOM danielpalme/ReportGenerator#380
• Update all calls to XDocument.Save to use an XmlTextWriter without a UTF-8 BOM encoding. danielpalme/ReportGenerator#381

[ahsonkhan]

1 is about the build directory

You can invoke the tool using the following command: reportgenerator
Tool 'dotnet-reportgenerator-globaltool' (version '4.6.6') was successfully installed.
You can invoke the tool using the following command: reportgenerator
Tool 'dotnet-reportgenerator-globaltool' (version '4.6.6') was successfully installed.

This latest version of the tool has the BOM fix.

[vhvb1989]

For src files I understand we would get compilation warnings,
but for non-src files like eng files and build (cmake), what's the benefit?

[ahsonkhan]

but for non-src files like eng files and build (cmake), what's the benefit?

Consistency (especially around the BOM) and I don't currently see a harm or reason to exclude them. If we find one in the future, we can skip those.

[vhvb1989]

Suggested a way to simplify scrip by just using recursive grep instead of a loop