feat: support github commit

[conwnet]

Support the url looks like https://github.com/conwnet/github1s/commit/39f10618df450771389d01bc88d117deaf79eedf
#236

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/vscode-github1s/github1s/C64vs1ZQNwCdb4MmZ1PnhJRuydHJ
✅ Preview: https://github1s-git-feature-commit-vscode-github1s.vercel.app

[Siddhant-K-code]

LGTM!

[xcv58]

We might need to consolidate the maps into two maps, since the maps are used as cache layers.

I think we should adopt a HTTP request client or invent a cache level on the network call side instead of put maps here.

For example, if we leverage the Got, which has built-in cache support:
https://github.com/sindresorhus/got#cache-adapters

We could remove all the maps and this file can be significantly simplified.

for example

	public getCommit = reuseable(
		async (
			commitSha: string,
			forceUpdate: boolean = false
		): Promise<RepositoryCommit> => {
			const [owner, repo] = [this.getOwner(), this.getRepo()];
			const key = `${owner}+${repo}+${commitSha}`;

			if (!this._commitMap.has(key) || forceUpdate) {
				const commitData = (await getGitHubCommitDetail(
					owner,
					repo,
					commitSha
				)) as RepositoryCommit;
				this._commitMap.set(key, commitData);
				this._commitFilesMap.set(key, commitData.files);
			}

			return this._commitMap.get(key);
		}
	);

->

	public getCommit = reuseable(
		async (
			commitSha: string,
			forceUpdate: boolean = false
		): Promise<RepositoryCommit> => {
			const [owner, repo] = [this.getOwner(), this.getRepo()];
			return getGitHubCommitDetail(
				owner,
				repo,
				commitSha
			) as Promise<RepositoryCommit>;
		}
	);