Fix #769 by setting PSUseConsistentWhitespace.CheckOperator to $false in default settings profiles

[RylandDeGregory]

PR Summary

Fix default settings profiles by implementing @kapilmb's workaround in the original issue of disabling the CheckOperator attribute of PSUseConsistentWhitespace.

Also aligned the assignment statements within all the default settings profiles.

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 .cs, .ps1 and .psm1 files have the correct copyright header
• Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
• 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.

[ghost]

All CLA requirements met.

[RylandDeGregory]

Seems as if the Pester tests are configured to where this can't possibly work. As both rules are being evaluated in different tests, they both need to be enabled.

I guess the actual issue is why the pester tests don't catch the issue that we (#769, #1460, #1490, #1556) have all been running into?

[bergmeister]

Sorry, this issue cannot be easily solved like that. For example, it would regress the behaviour of Invoke-Formatter -ScriptDefinition '$a=1' whereby at the moment it formats it to $a = 1 but with your change it would format to $a=1. Therefore this would not be acceptable to the majority of users. I suggest you create your custom settings file if that is what works for you in the meantime. We also had an alternative and preferred PR #1566 which looks very promising as it does not cause user regressions and will solve your issue and I am very positive that other PR will get merged, therefore expect the proper fix to be in the next version. Thank you for your efforts though.

[RylandDeGregory]

I realized the same after doing some testing and running it through the Pester harness within this Repo. I'm glad it's finally being addressed though. Thanks.