Package.json updater depends on vscode environment

[abaljeu]

The effect of this dependency is two-fold:

1. When you make changes to the package definition (through package.ts) you need to compile, run, quit, run, because the run updates package but vscode can't accept updates after it already loaded the extension.
2. It's more convoluted than necessary to understand the bindings.

I am working on a refactoring that retains the command generator functions, but separates them from the action objects. Exactly what this will look like remains to be seen but I aim to keep and improve the clean structure of the code base. It's a major change though, so I don't know if Ding wants this.

(My ideas, of changing behavior of this extension, remain ideas; these code changes should be purely structural.)