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

This makes the documentation parser sort the CI variables before
comparing a difference.

docs: separate custom query documentation into a new file

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

feat: add "Merge requests I'm reviewing" custom query

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

feat: only poll for new status bar information in focused window

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

During the refactoring, we had to disable one test that hid the MR
status bar item when there wasn't any project. This commit fixes the
scenario by checking whether a GitLab project can be fetched for the
current workspace and if not, we hide all the status bar items. This
also happens to fix the #71.

The "init" keyword wasn't accurate anymore. We were simply creating the
StatusBarItems and it made more sense to inline the creating so the
reader instantly knows what's happening.

When there is no workspace folder, we will skip refreshing all together.
This scenario can occur when user didn't open a project, or they use
multi-root project and don't have a file open in the editor.

This commit changes the `refreshPipelineAndMr` method to refresh all
status bar items. Instead of using the class properties to communicate
between methods, we are passing values to the `updateMrItem` and
`fetchMrClosingIssue`. This makes the code easier to reason about
because there is fewer side-effects