Investigate/Fix test failure on PowerShell Core

[bergmeister]

• The "suggests corrections for AliasesToExport with wildcard of UseManifestExportFields is currently set as pending when tests are being run using the coreclr. This tests needs to be looked into and possibly fixed. The test is here: https://github.com/PowerShell/PSScriptAnalyzer/blob/021711eae27a2bd00165f30c6c568a78f448870a/Tests/Rules/UseToExportFieldsInManifest.tests.ps1#L86
• There are 9 test failures using PowerShell Core on Windows and Ubuntu but they do not fail in AppVeyor for some reason. Those tests were always failing, even when going back to an old commit like 9e37dd34e8564dc7470dda1e0d2596de37bcd679 in January. Therefore those failures are to be considered technical debt. Until we know why AppVeyor lets them pass and fix them afterwards, we have to more diligent with running tests locally or on VSTS using PowerShell Core to make sure that we do not introduce regression. The test failures are:

[bergmeister]

I found the reason now: locally I have en-GB culture but the CommunityAnalyzer module that is used by tests provides only locale for en-us, this is probably a PSCore bug (changing the language folder to match my locale makes it work, which is not required in Windows PowerShell)