Converts GitHub integration authentication to use gk.dev GLVSC-554

[sergeibbb]

Description

Introduces a provider for GitHub integration that tries to check for existing GitHub session before accessing an integration on GKDev (GLVSC-554)

Checklist

• I have followed the guidelines in the Contributing document
• My changes follow the coding style of this project
• My changes build without any errors or warnings
• My changes have been formatted and linted
• My changes include any required corresponding changes to the documentation (including CHANGELOG.md and README.md)
• My changes have been rebased and squashed to the minimal number (typically 1) of relevant commits
• My changes have a descriptive commit message with a short title, including a Fixes $XXX - or Closes #XXX - prefix to auto-close the issue that your PR addresses

[axosoft-ramint]

A couple of suggestions on the base class and override strategies - mainly suggesting that we leverage abstract classes/fns.

[axosoft-ramint]

Apologies for multiple reviews - one more important thing I forgot in the previous review regarding "connect to remote".

[axosoft-ramint]

Currently, when testing with a GitHub repo on this PR branch, it shows that my remotes are not connected, and Launchpad also doesn't recognize my existing (VScode built-in) connected GitHub integration.

I did a bit of investigation and found out why - we covered existing built-in GitHub tokens in the createSession flow, but not in the getSession flow.

[axosoft-ramint]

Hey @sergeibbb, while reviewing your PR, I'd suggest the following code changes:

👉 Fixes integration.connect throwing error for GitHub

Ensures that manageCloudIntegrations is always called before attempting integration.connect for GitHub

You can also review and apply these suggestions locally on your machine.

Learn more about GitKraken Code Suggest

Code Suggest liberates your code reviews from GitHub's restrictive, comment-only feedback style. As simple as suggesting changes in a Google-doc, provide real code suggestions from where you code, e.g. your IDE, and on anything in your project — not just on the lines of code changed in the PR.

Join your team on GitKraken to speed up PR review.

[axosoft-ramint]

@sergeibbb There are issues with integration.connect being called on a cloud integration before it is ready. manageCloudIntegrations should always be called before attempting the connection, or the user may not be logged in or may not see the settings page first.

I made some updates to address this - see my code suggestion above.

[d13]

This is looking great. I've been able to successfully test:

• With local integration, without GK integration
• With GK integration, without local integration
• With local integration fallback, after signing out of GK integration