Glory to the Monorepos

[novusnota]

Or just using workspaces of Yarn v1.

Current issues

1. Docs package, although deployed to docs.tact-lang.org and not published to npm, requires some Tact compiler functionality.
2. Each package in the repo (compiler, docs) require their own set of dependencies with some overlap, where cspell is used in both places and requires to be installed in both
3. Other essential developer tools utilizing the compiler (lsp, formatting, linting*, docgen*) are tough to version, develop and manage since they are not present in the same repo with the compiler, which means that they easily drift away from it and require constant vigilance from users and developers to make sure that compatible versions of each are used together.

Proposed solution

1. Move all packages (tact compiler, docs) into the newly created workspaces or packages directory.
2. Make a root of the compiler repo a private: true package designated to control the workspaces.
3. Set up dependencies in packages (docs): to use @tact-lang/compiler: "*" with yarn doing the rest.

Then, running yarn (i.e. yarn install) would take care of common dependencies AND of cross-dependencies of one "workspace" (package) on another.

Finally, by running yarn workspace WORKSPACE_NAME as a prefix, one could run any yarn command inside any particular workspace while being anywhere in the repo tree.