fix(powershell_es): update LogLevel to recognized value

[seejaysea-dev]

Problem:
Powershell Editor Services does not recognize -LogLevel Information and this prevents the LSP from starting

Solution:
Revert update to command_fmt to use a recognized log level from Start-EditorServices.ps1

[seejaysea-dev]

fixes bug #3918

[sharpchen]

I think we should revert #3914

[seejaysea-dev]

Ah, I didn't see that PR

[seejaysea-dev]

Updated to revert commit

[justinmk]

#3914 notes that Normal was removed in PowerShell/PowerShellEditorServices@d9de5bd , do we need to decide this based on the LS version ?

[sharpchen]

@justinmk The issue is the wrapper script Start-EditorServices.ps1 has an outdated validation that doesn't allow new log levels, which caused the error. Normal will be deprecated in the future but currently still available, so we don't have to decide on ls version, once the pwsh_es updated the log level validation we can change it to Information again.

https://github.com/PowerShell/PowerShellEditorServices/blob/3a429eac5544fd7613c281c0814f94ac03fad551/module/PowerShellEditorServices/Start-EditorServices.ps1#L49

[eitamal]

I've opened with PowerShell/PowerShellEditorServices:

• Issue: Missing MEL levels from LogLevel param in Start-EditorServices.ps1 PowerShell/PowerShellEditorServices#2235
• PR fixing the issue: Add missing MEL log levels to the LogLevel validation (#2235) PowerShell/PowerShellEditorServices#2236

So, hopefully it'll be fixed soon :)

Maybe worth noting, they've added some conversion code for backwards compatibility: StartEditorServicesCommand.cs which covers Normal -> Information - so there shouldn't be any urgency in getting the change back to Information out (in case there was any).

[seejaysea-dev]

Thanks @eitamal. I was hoping to get the time to do almost this exact PR today in PES