chore/docs: Update CONTRIBUTING pointing to sourcegraph/cody (#2811)

JetBrains plugin development has moved to the sourcegraph/cody repo.

## Test plan

No tests; docs-only change.

Bump cody.commit to match vscode-v1.48.1

bump commit to vscode-v1.48.x

bump commit to vscode-v1.48.x

[Backport jb-v7.4.x] Fix crash on Edit Code (#2705)

First I tried to simply setActiveAccount for the deprecated manager.
This is not the best solution as do not know some values for the account
(`name`, `displayName`, `id`). We could hardcode some values but we
would be persisting some artificial data for a simple task that is -
**all we need is to store the llm that was used for Edit Prompt most
recently**.

So instead of hacking & mocking the deprecated logic (HistoryService
is used basically only for history reasons, migrations, etc)... instead
of that, let's simply use a simply dedicated storage class.

Also, it could be an actual storage with a corresponding storage file
(.xml) but do we really need it? Project session persistence should the
enough for most users.

Show cody console only in dev mode (#2694)

## Test plan

**Scenario 1**

Run new IJ instance using `:customRunIde` and make sure that:

a) When debug logging is disabled cody console does not show up during
normal operations
b) When debug logging is enabled cody console show up after some time

**Scenario 2**

Build plugin and instal it by choosing zip package form disk. Make sure
that:

a) When debug logging is disabled cody console does not show up during
normal operations
b) When debug logging is enabled cody console **also does not show up**

bump commit to vscode-v1.48.x (#2691)

bump cody commit to head of v1.46.x

bump cody commit to head of v1.46.x