Improve or remove reporting on VS Code extension sign in issues

Currently we make it very easy for the user to file a GitHub issue when they encounter an error signing in while using our VS Code extension. However, we inevitably need follow up information (like whether or not they explicitly aborted the sign in) and we almost never get a response from the user. As it stands, these issues are noise.

We should either improve the data we collect at the point of the failure, or stop reporting these failures since they aren't actionable.

Start by locating the VS Code extension's sign-in failure reporting and the path that files a GitHub issue. Review what information is available when sign-in fails and determine whether the actionable outcome is improved context collection or no issue creation; done when the chosen behavior is implemented and verified.

Written by the indexing model from the issue text.