Investigate auto-sign-in issue in vscode.dev

[justinrobots]

User reported in discussion ( #3930) that they were forced to sign-in with GK account and start a trial after installing GitLens on vscode.dev.

We suspect this has something to do with GitLens needing to have a connection with GitHub to get information from the repository and triggering our GItHub integration flow to satisfy that on vscode.dev.

To reproduce for testing, we will need to start with a clean environment that doesn't have any previous connections to GitHub.

Ultimately, users should not be required to create an account or start a trial to use GitLens unless they are using features that require an account.

[axosoft-ramint]

Repro steps:

1. In a fresh environment (incog tab for example), open a vscode.dev url that includes a GitHub repository
2. Should immediately be prompted to auth with GitHub. Complete the auth.
3. Install GitLens.

Expected: A prompt that GitLens wants to sign in with GitHub (using the existing built-in GitHub auth)
Actual: Attempts to connect GitHub cloud integration via a link to gkdev

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.