Since integrating our repos, there have been a number of changes in PRs that touch the encoding of the file, adding or removing a BOM as the editor in question decides. I've standardized on UTF-8 with BOM, as we do in roslyn, and put it in the .gitattributes so it should hopefully stay consistent.
* Add Rich Nav task to normal CI, add new Rich Nav pipeline
* Fix typo
* Try getting _BuildConfig value from variables
* Temp: fix eng script that's broken in arcade to test rich nav pipeline
* Add Rich Nav feed to Nuget.Config
* Fix regular CI to actually run Rich Nav for windows builds
* Remove Rich Nav from regular CI, respond to PR feedback
* Fix typo, start specifying language
* Fix typos in Rich Nav script discovered while executing the build