This is to be reverted in the next MR. This disabling is used instead of
a feature flag. Now the preliminary refactoring can be reviewed
separately.

We crated a fragment that contains all note information. We then use
this fragment for fetching discussions and for returning note from the
createNote mutation. We also had to fix the webview integration test
where the fake API response must now contain the note.

The real reason for this simplification is summed up in the following
line:

```
export type GqlNote = GqlTextDiffNote | GqlImageNote | GqlOverviewNote;
```

We can now refer to notes by GqlNote instead of having to specify
generic arguments. That makes the code easier to read and it will allow
us to return GqlNote from the createNote mutation.

Excluding the position from overview notes was a small optimization.
Removing the condition simplifies the code at the cost of small
overhead (currently roughly 20 requests per hour).
After this change we'll always fetch the diff position.

If the comment changed on the server, but the extension still
shows the old version, we'll prevent the extension from overriding
the server's latest version. We'll warn the user that the
comment has changed since they last saw it.

Introduce startEdittingComment and cancelEdittingComment
commands that will open and close the VS Code comment
text area. The cancel command also resets the comment body
to the value retrieved from the API.

This is marked as refactor, because we don't want this commit to have
a line in the changelog. It's an uncomplete feature.

This prevents confusion between GitLab project and VS Code workspace.
The current legacy naming that uses the name "project" to represent
VS Code workspace is diverging from an established naming and
confuses contributors.

The work "project" is used throughout the codebase for GitLab project
and it was causing confusion when two variables named 'project' meant
different things.

This command prefixes the path opened by the “Copy link to active file
on GitLab” and “Open active file on GitLab” commands.

This is useful to fix the link generated by the above file link commands
if your VS Code workspace root isn’t the git root.

All logic related to creating vscode.CommentThread and
setting the correct properties has been extracted to one class.

This class will be responsible for resolving threads in the future.

The GitLabComment is going to be responsible for all comment-related
functionality like editing, deleting and reacting.

A simple implementation of the git.clone command for the configured
instances.
It also includes a credential provider that can clone the repository
without user input using the access token

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

Relates to #222

After implementing detached pipelines, this method is only used within
the gitlab_service module.

We had to change the command for openning pipeline in the browser
to support detached pipelines.

All the data we need are in the API response that lists pipelines.

Prefer detached pipelines and only report normal branch pipeline when
there isn't any detached pipeline (MR pipeline).

We also change the logic to fetch MR and pipeline at the same time
because we need to know MR anyway to be able to get detached
pipeline.

Refactoring status_bar to use both pipeline and MR from the response
is too difficult to squeeze in this change. We'll have to do it later.

This reduces the need for readers to keep a variable
in their head to read 50 LOC.

By relying on an exception, we are able to remove several checks
for failed project fetching. This also saves one extra call to
the /project endpoint. Additionally, this commit replaces a long
if statement with an early return.