Closes#588

This PR refactorsstorage.ts into small, isolated modules that are straightforward to unit test (with mocks). It also upgradesvitest to a version that plays nicely with VS Code extensions, so we can view coverage, run and debug tests directly in VS Code.

VS Code Test Explorer:

Why mockvscode?

With the current VS Code Extension API, we essentially have two testing layers:

• Unit tests (mockedvscode) : Validate our module's behavior independently of the VS Code API and external calls (e.g., Axios). These are fast, reliable, and cover most logic.
• Integration/E2E tests (real VS Code): Exercise "real" user flows by launching VS Code and, eventually, a server. These are valuable but more limited, since UI interaction is hard to automate and not all code paths are easily reachable.

By mockingvscode for unit tests, we keep feedback tight and deterministic, while reserving integration tests for end-to-end scenarios that require the actual runtime.