In order to allow devs to test the extension e2e locally, they can either build and sideload it locally, or use the extension that is built on every PR.
The problem is that VS Code can't conveniently manage side loaded extension, causing them to conflict inside VS Code.

Known conflicts:

• They both appear the same in the extension tab, making it impossible to delete just the sideloaded extension
• There will only be one @kupilot agent in the chat
• No ability to configure both in settings

Also, I am not sure what is the behavior when the extension is debugged. Possibly, that is a 3rd flow of conflicts.

Acceptance Criteria:
All conflict flows should create a "dev" extension that does not compete with the release one (extension name, agent name, settings, etc.)