Update to powershell grammars

[Nick James (omniomi)]

This is an incremental update from https://github.com/PowerShell/EditorSyntax

• Handful of scope corrections and fixes.
• One bug fix with comment documentation.

Our tests are passing: (https://ci.appveyor.com/project/powershell/editorsyntax/branch/master)

Running specs...

...

Finished in 21.437 seconds
367 tests, 3524 assertions, 0 failures, 0 skipped

as are the vscode-colorize-tests:

colorization                                            spec.js:40
...
√ powershell-test.ps1 (455ms)                           spec.js:67
...

[Nick James (omniomi)]

Martin Aeschlimann (@aeschli) do you need anything from me to merge this update to the PowerShell grammar? The build failed because master was broken when I forked it. If you want me to merge in the current master I can.

[Nick James (omniomi)]

Martin Aeschlimann (@aeschli) I merged the latest master and now the tests are failing. It seems to indicate 'source.powershell comment.line.powershell punctuation.definition.comment.powershell' was the issue but it doesn't indicate what it was expecting or what it got. On the latest version on insiders the comment opener # matches the test file using the latest syntax . https://vscode.visualstudio.com/VSCode/_build/results?buildId=3289&view=ms.vss-test-web.test-result-details

This PR also doesn't touch the comment scopes except for "comment.documentation.embedded.powershell"

Can you please point me at how I figure out what exactly your tests are doing?

Pinging TylerLeonhardt into the loop.

[Martin Aeschlimann (aeschli)]

I pushed a new commit with the updated grammar and tests.

[Martin Aeschlimann (aeschli)]

Thanks Nick James (@omniomi). Instead of trying to fix merge issues, I suggest to just rerun the integration tests ( scripts/test-integration.sh(bat)). The test takes the entries in test/colorize-fixtures and runs the grammar and theme rule matching on it. The result is written to test/colorize-result. If the written result is identical to the previous result or contains only scope name change, the test is green, else it is red. Use the Git diff viewer to see the differences in the result. If all changes make sense, accept the new result by committing it.