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.

Backport security release 3.15.1 back to main branch

See merge request gitlab-org/security/gitlab-vscode-extension!8

fix: use the same git binary as VS Code

See merge request gitlab-org/security/gitlab-vscode-extension!7

refactor: refactor fetchIssuables to use URLSearchParams

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

docs: remove branch rename notice

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

feat(mr review): editing comments on MR diffs

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

Fix broken extension packaging

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

chore(ci variables): update the ci_variables.json

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

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.

refactor: rename objects representing workspace

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

chore(npm): run npm upgrade to update all dependencies

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

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.

fix: workspace in project subfolder breaks Open active file on GitLab

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

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.

Convert typescript integration tests to unit tests

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

feat(mr review): deleting comments on MR diff

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