Replace StringComparision.CurrentCulture with StringComparision.Ordinal

[iSazonov]

PR Summary

Related #8064

Replace StringComparision.CurrentCulture with StringComparision.Ordinal.

Best Practices for Using Strings in .NET

Not all code base is fixed. There are not obvious cases.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Change is not breaking
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.
• User-facing changes
  • Not Applicable
  • OR
  • User-facing Documentation needed
    • Issue filed - Issue link:
• Testing - New and feature
  • Not Applicable or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
    • Add [feature] if the change is significant or affects feature tests

---

This change is 

[TravisEz13]

---

src/Microsoft.WSMan.Management/WSManConnections.cs, line 143 at r1 (raw file):

            {
                computername = value;
                if ((string.IsNullOrEmpty(computername)) || (computername.Equals(".", StringComparison.OrdinalIgnoreCase)))

I've seen this in many places, perhaps we should have a central place for this code?

[TravisEz13]

Reviewed 24 of 24 files at r1.
Reviewable status: complete! all files reviewed

[TravisEz13]

We probably should fix this one as well:

PowerShell/src/System.Management.Automation/engine/parser/SafeValues.cs

Line 641 in 2f1863a

Hashtable hashtable = new Hashtable(StringComparer.CurrentCultureIgnoreCase);

[TravisEz13]

Thinking about it further with @JamesWTruher , Hashtable could be culture sensitive in some cases. This should be a different PR and probably be behind an experimental flag.

[iSazonov]

Hashtable could be culture sensitive in some cases.

@TravisEz13 In the PR I fixed only obvious cases. There are still about 30 unclear cases left. It would be great if MSFT team reviewed them.

I've seen this in many places, perhaps we should have a central place for this code?

If we should please open a tracking issue and I'll fix this later.