feat #7892: support vsc ext create pseudo terminal

[datou0412]

Signed-off-by: 二凢 dingyu.wdy@alibaba-inc.com

What it does

Support API vscode.window.createTerminal with option ExtensionTerminalOptions

• In plugin process, store _pseudoTerminals in memory
• TerminalServiceMainImpl listen to terminal widget events and call _pseudoTerminals&widget methods through proxy
• TerminalWidgetImpl fire events and expose methods.
• Create a pseudo terminal process named asPseudoPty in backend.

Plugin Process <--proxy--> TerminalServiceMain <--Events&Methods--> TerminalWidget <--proxy--> Shell Process

How to test

Install any extension which use the api vscode.window.createTerminal with option ExtensionTerminalOptions

• package this extension with vsce and move the .vsix file to plugins folder
• yarn start:browser
• cmd+p -> Extension Terminal Sample: Create

Just input anything

Resize your window

Review checklist

• as an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• as a reviewer, I agree to behave in accordance with the review guidelines

[akosyakov]

Install an extension which use the api vscode.window.createTerminal with option ExtensionTerminalOptions

It would be good to have something more concrete steps for reviewers.

Maybe this one can be used to test

Maybe sounds like you did not test your changes. How to test section should show that you know how to test and share it with others.

[datou0412]

Install an extension which use the api vscode.window.createTerminal with option ExtensionTerminalOptions

It would be good to have something more concrete steps for reviewers.

Maybe this one can be used to test

Maybe sounds like you did not test your changes. How to test section should show that you know how to test and share it with others.

I have tested my changes with the extension. Maybe i should remove Maybe :p

[akosyakov]

Code looks quite good. I hope it works as good too, someone has to test it.

[akosyakov]

@datou0412 Could you add fix marker in the description for issues which will be resolved with it? see https://help.github.com/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords

[datou0412]

Code looks quite good. I hope it works as good too, someone has to test it.

I have fixed all conversation issues, re-review is welcomed

[paul-marechal]

Code LGTM, I'll let Anton review the widget-api/storage aspect.

[akosyakov]

tested with the sample vscode extension and it behaves in the same way as in VS Code

Please get rid of commits fixing issues introduced by the PR. One commit will be enough. Please see: https://github.com/eclipse-theia/theia/blob/master/doc/pull-requests.md#checklist-commit-history