fix: limit command availability

See merge request gitlab-org/gitlab-vscode-extension!244

This commit limits when is it possilbe to run a command.
Most of the commands should not be run if the extension
isn't in a valid state (e.g. no repository or token)

ci(eslint): update @typescript-eslint from 3.10.1 to 4.22.0

See merge request gitlab-org/gitlab-vscode-extension!242

ci(eslint): update eslint from 6.8.0 to 7.25.0

See merge request gitlab-org/gitlab-vscode-extension!241

Replace node-sass with sass

See merge request gitlab-org/gitlab-vscode-extension!240

feat(side panel): use git repositories to look for GitLab projects

See merge request gitlab-org/gitlab-vscode-extension!239

Signed-off-by: NTakuya Noguchi <takninnovationresearch@gmail.com>

Signed-off-by: NTakuya Noguchi <takninnovationresearch@gmail.com>

Signed-off-by: NTakuya Noguchi <takninnovationresearch@gmail.com>

This will enable us to attach logic to repositories in the future.
For example, we'll add GitLab API service to each repository to simplify
how we call API.

When the git extension got disabled, we called dispose() on the wrapper.
This dispose() method removed the listener that should have listened on
when the git extension gets enabled again.
The solution for this problem was to separate the enablement listener.

Instead of using workspaces, we now use the repositories from
VS Code git extension to look for which projects should we show in
the sidepanel

The issuable data provider is the only client of the method and thanks
to this refactoring we can start changing the way how we find all
projects within the workspace without adding more dependencies
to the legacy gitlab_service

chore: update CI variables

See merge request gitlab-org/gitlab-vscode-extension!238

docs: add notice to enable fork repo mirroring

See merge request gitlab-org/gitlab-vscode-extension!236

feat: show welcome view when there is no git repository

See merge request gitlab-org/gitlab-vscode-extension!235

docs: update outdated sign up link

See merge request gitlab-org/gitlab-vscode-extension!237

feat: add commenting ranges for new file versions in diff

See merge request gitlab-org/gitlab-vscode-extension!234

We were mistakenly showing the "Could not get Git Extension" message
during every extension startup.

Thanks to @Musisimaru for noticing that we forgot to put the wrapper in
the list of subscriptions.

refactor: reduce eslint warnings

See merge request gitlab-org/gitlab-vscode-extension!217

We parse the MR version REST API response into hunks. These hunks tell
us what lines have been added in the new file version on the diff.
We then convert these lines in VS Code Ranges and return them as ranges
on which the user might leave a comment.

add commenting range for old files in the MR diff

See merge request gitlab-org/gitlab-vscode-extension!232

refactor: change git_service to always requrie workspaceFolder

See merge request gitlab-org/gitlab-vscode-extension!233

ci: add junit reports

See merge request gitlab-org/gitlab-vscode-extension!183

Fix CI variables update script compares order of items

See merge request gitlab-org/gitlab-vscode-extension!230