Fixes https://linear.app/sourcegraph/issue/CODY-3132

## Changes

1. `extensionConfiguration_didChange` is not called anymore on every
opening of the file. It was used to set `cody.codebase` settings key on
the Cody side. But it should not be needed, as[ it should always be
obtained from the currently opened
file](https://github.com/sourcegraph/cody/blob/main/vscode/src/repository/git-metadata-for-editor.ts#L53)
anyway.

## Test plan

1. Create git test project 
2. Edit `.git/config` file and change `[remote "origin"]` to contain url
like:
`url = git@github.com:122345/a/b/c/my-Repo.git`
3. Run IntelliJ and switch files few times - there should be no errors
(in fact that code path is not executed anymore)
4. Click right mouse button, `Sourcegraph` > `Open Selection In
Sourcegraph Web`
5. It should fail, but URL should start with
`https://sourcegraph.com/github.com/1234/sourcegraph/a/b/my-Repo/@main/-/blob/`

Related to https://github.com/sourcegraph/cody/pull/5871.

In this PR we make use of the recent changes ☝️ we remove some redundant
calculations for completion text.
Additionally, we properly derive the insertion text and the position for
the inlay. That makes the inlays look more fancy and precise.

Note that Remote Dev does not use inlays. Some completions won't look
that nice there yet (but it is no worse).

## Demo 

### Before  

https://github.com/user-attachments/assets/805c9012-7393-45fd-8d9f-22ae4cd5bf30

### After

https://github.com/user-attachments/assets/d5c2e7b6-4bc9-4ee5-ab8c-4f9c427915aa

## Test plan

Autocomplete works in all cases

| | remote dev | regular |
| --- | --- | --- |
| single line | Case 1 | Case 2 | 
|  multi line | Case 3 | Case 4 |

…2450)

## Changes

1. Fixed `InlineCompletionProviderID` package
2. Added a few comments

## Test plan

N/A, it is related to the test/verification infrastructure.
It should decrease amount of compatibility issues reported by
verification job on the marketplace.

Updates the JetBrains marketplace page.
- Changes "Commands" to "Prompts"
- QOL updates to sync against the VSC marketplace

## Test plan

Marketing copy update only.

)

This is the JetBrains half of the
[CODY-1043](https://linear.app/sourcegraph/issue/CODY-1043/bug-account-credentials-are-cached-between-installs),
the VSC half of it is in [this
PR](https://github.com/sourcegraph/cody/pull/5819).

For VSCode I was able to write an E2E as there are electron & VSCode
test utilities for opening / closing instances of VSC and installing /
uninstalling plugins.

Does anyone know if we have similar utilities that we could use to write
a test for this behavior in JB?

The good news is that JB actually has proper APIs for this hook so the
complexity is much lower here.

## Test plan
I manually tested this by running `CODY_DIR='<my local cody>' ./gradlew
-PforceAgentBuild=true buildPlugin` and then opening the plugins menu
and installing a plugin from disk.

![image](https://github.com/user-attachments/assets/0b0c7482-9dce-4ce5-8f80-07b60857e1d9)

I logged in and then uninstalled from the same menu. After reinstalling,
it takes me back to the login screen and all previous endpoints are
cleared. When I log back into the same account I see my chat history is
removed.

The code was used in the chat in the deprecated UI. We do not need it
anymore.

## Test plan
1. N/A

Fixes
https://linear.app/sourcegraph/issue/QA-122/jetbrains-crash-occurred-while-clicking-on-file-name-from-chat-context.

## Test plan
1. Follow the repro steps from the QA report - that is, run Explain Code
and try the context files navigation links

Resolves
https://linear.app/sourcegraph/issue/CODY-3753/make-it-possible-to-automatically-switch-user-runtime-to-one-which.

## Test plan 

### Dev run (`:customRunIde`)
1. Modify `build.gradle.kts`. Change
  ```
dependencies {
  intellijPlatform {
    jetbrainsRuntime()
...
  ```
  to
  ```
dependencies {
  intellijPlatform {
    jetbrainsRuntimeExplicit("jbr-21.0.3-osx-aarch64-b446.1")
...
  ```
so that the IDE will use no jcef runtime at the start. 
2. `:customRunIde`
3. Verify the notification appears
4. Verify the proper panel appears

Adding `repo/jetbrains` label to help distinguish where the issue came
from when we sync it back to linear. Will also do the same to the Cody
repo so that we have one single point of entry for all bugs

## Test plan
N/A

<!-- All pull requests REQUIRE a test plan:
https://sourcegraph.com/docs/dev/background-information/testing_principles

Why does it matter?

These test plans are there to demonstrate that are following industry
standards which are important or critical for our customers.
They might be read by customers or an auditor. There are meant be simple
and easy to read. Simply explain what you did to ensure
your changes are correct!

Here are a non exhaustive list of test plan examples to help you:

- Making changes on a given feature or component:
- "Covered by existing tests" or "CI" for the shortest possible plan if
there is zero ambiguity
  - "Added new tests"
- "Manually tested" (if non trivial, share some output, logs, or
screenshot)
- Updating docs:
  - "previewed locally"
  - share a screenshot if you want to be thorough
- Updating deps, that would typically fail immediately in CI if
incorrect
  - "CI"
  - "locally tested"
-->

## Test plan

Full QA is needed.

) (#2434)" (#2484)

This reverts commit 65f65c5.

The UninstallListener introduced in this commit seems to run for every
extension uninstall instead of just when the sourcegraph extension is
uninstalled.

## Test plan
This will need to be manually tested.

## Test plan

Full QA

## Changes

1. Fixed package for `InlineCompletionSuggestion`
2. Added separate versions of `CodyInlineCompletionProvider` for IJ 2023
and 2024 (although 2024 version will be used only if `platformVersion`
is changed explicitly, e.g. using `-PplatformVersion=2024.2`).
3. Fixed build definition issues for IJ 2024, mostly connected with
missing VCS packages.

## Test plan

Verify that completions and opening Revision Diff in Sourcegraph Web
works:

* In IntelliJ 2023.2
* In IntelliJ 2024.2
* In IntelliJ 2024.2 in split mode (or using remote directly)

## Changes

Fixes BUGS-577 

In IJ 2023 we want `CodyInlineCompletionProvider` to be disabled, but we
need to load the class to make the check.
`InlineCompletionProviderID` class does not exist in 2023.2 and younger,
so loading class was failing.

## Test plan

1. Open IJ 2023.2 and check if autocomplete works. No exception should
be thrown.
2. Open IJ 2024.2 in remote mode and check if autocomplete works. No
exception should be thrown.

## Changes

It contains fix for
https://linear.app/sourcegraph/issue/QA-130/jetbrains-429-error-occurred-when-clicking-on-filename-from-chat

## Test plan

Full QA.