Quick start doc in README

[TylerLeonhardt]

fixes #1057

Note, this is not exhaustive but I wanted to write something down to at least give folks a place to start.

In theory a more exhaustive doc should be elsewhere (like on docs.microsoft.com) but this will do for now.

[rjmholt]

This is very good information.

I don't want to prescribe too much in terms of style or tone, but could if you like.

Some things it might be worth mentioning:

• Why Stdio doesn't support the Integrated Console
• What startup looks like and what the timing is between client and server (so people don't think the script has hung)
• Security considerations for clients using named pipes
• How shutdown works and the lifetime of the server compared to the client
• What we consider to be stable and what clients can depend on (messages vs linking)
• Why debugging with PowerShell is a bit different (i.e. happens in the same process)

[TylerLeonhardt]

I agree with what you're saying but I think a lot of what you're suggesting should be in a more exhaustive doc instead of a quick start that this is trying to be.

[TylerLeonhardt]

Why Stdio doesn't support the Integrated Console

Added

What startup looks like and what the timing is between client and server (so people don't think the script has hung)

Added

Security considerations for clients using named pipes

Should be in a different doc

How shutdown works and the lifetime of the server compared to the client

Should be in a different doc

What we consider to be stable and what clients can depend on (messages vs linking)

Added

Why debugging with PowerShell is a bit different (i.e. happens in the same process)

Added