Fix RCS1033: Remove redundant boolean literal part 1

[xtqqczze]

PR Summary

Changes should be reviewed with commits combined.

Autofix RCS1033: Remove redundant boolean literal

Due to size, changes to System.Management.Automation were excluded and will be presented in a seperate PR.

PR Context

#13334

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• 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: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • [NA] Experimental feature(s) needed
    • [NA] Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • [NA] Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • [NA] Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • [NA] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[xtqqczze]

@iSazonov Can you review, again :(

[xtqqczze]

@TravisEz13 can you please review?

[rjmholt]

@xtqqczze what's the full size of all the changes for this? We need to understand the risk for things like commit conflicts and cherry picks. For this and some other style changes, it may be worth opening tracking issues so that work can be broken down into manageable pieces.

[daxian-dbw]

@PowerShell/powershell-maintainers reviewed this PR and agreed to accept it for 7.2-preivew. So we should delay merging it until after 7.1-RC1 release branch gets created.

The changes make sense and the chance of confliction is relatively low, but it requires line-by-line review to make sure there is no potential incorrect change, so it's better to delay merging it till 7.2 preview to avoid possible regression.

[iSazonov]

Set to Draft till 7.2 Preview1.

[ghost]

This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 15 days. It will be closed if no further activity occurs within 10 days of this comment.

[ghost]

This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 15 days. It will be closed if no further activity occurs within 10 days of this comment.

[iSazonov]

@rjmholt @SteveL-MSFT I think we can merge.

[xtqqczze]

CodeFactor issues are pre-existing.

[xtqqczze]

@rjmholt Could you help merge, this is blocking #13833.

[ghost]

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author

[iSazonov]

@xtqqczze Please resolve merge conflicts.

[ghost]

🎉v7.2.0-preview.1 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes