Add new code formatting preset "OTPS": OTBS with else on new line

[Olav Rønnestad Birkeland (o-l-a-v)]

Edit: Blocked, see PowerShell/PSScriptAnalyzer#2045 (comment).

PR Summary

• Linked PR in PSSA: Add new code formatting preset "OTPS": OTBS with else on new line PSScriptAnalyzer#2158
• Linked PR in vscode-powershell that can be merged after this and the PR to PSSA: Add new code formatting preset "OTPS": OTBS with else on new line vscode-powershell#5413

This PR adds a new code formatting preset, "OTPS" (One True PowerShell Style): OTBS with else on new line.

PR Context

Thoughts behind the name:

• To mock the idea of one true formatting style, even though there are none.
• We do ONE change from OTBS (else on new line), also in the name (change B with P).

Feature request:

• New formatting preset: OTBS with else on a new line PSScriptAnalyzer#2045

Context:

• "There is no One True Brace Style": There is no One True Brace Style PoshCode/PowerShellPracticeAndStyle#177
  • About OTBS with else on a new line:
    • There is no One True Brace Style PoshCode/PowerShellPracticeAndStyle#177 (comment)
    • There is no One True Brace Style PoshCode/PowerShellPracticeAndStyle#177 (comment)

[Olav Rønnestad Birkeland (o-l-a-v)]

@JustinGrote:

PowerShell/vscode-powershell#5109 (comment)

So a PR could be fairly straightforward to just add a new entry to the enum with the appropriate settings. Changing the switch to an exhausive pattern matching would also help catch any net-new issues.

Do you mean a default case could catch both Stroustrup and this new proposed style OTPS as have the same values?