Publish cli crate

[ry]

• Combines cli_snapshots and js into one directory.
• Extracts TS version at compile time rather than runtime
• Makes publish work on deno_cli, deno_cli_snapshots, and deno_typescript
• bumps version awkwardly. sorry.
• adds new git submodule deno_typescript/typescript
• improves lint.py and format.py scripts

Try: cargo install deno_cli

Towards #2942

[kt3k]

LGTM

[piscisaureus]

• Makes publish work on deno_cli, deno_cli_snapshots, and deno_typescript

I don't see any updates to cargo_package.py. Am I missing something?

[ry]

I don't see any updates to cargo_package.py. Am I missing something?

So, the other crates (deno_cli, deno_typescript, deno_cli_snapshots) are able to be published with just "cargo publish". I think we should leave to cargo_package.py as it is, because it's doing a particular hack... I could add tools/cargo_publish_others.py (or something) that simply ran cargo publish in the various directories? But I think there are more clean ups to happen still in this area (in particular i want to still rename the crates so we can have 'cargo install deno' work), and I would just as well put that off for a while.

[piscisaureus]

So, the other crates (deno_cli, deno_typescript, deno_cli_snapshots) are able to be published with just "cargo publish". I think we should leave to cargo_package.py as it is, because it's doing a particular hack... I could add tools/cargo_publish_others.py (or something) that simply ran cargo publish in the various directories? But I think there are more clean ups to happen still in this area, and I would just as well put that off for a while.

Ok, that's great. I was mainly looking for it to understand what the release procedure looks like.
Which crates have to be published, in which order? What command do I run?

[piscisaureus]

I don't fully understand what the release procedure is after this, maybe add some explanation (see #2946 (comment)).

But it seems to work so go ahead and land.

[ry]

I've added tools/cargo_publish_others.py which shows the order they have to be run.

We should probably also be running this with the --dry-run argument in CI, because "cargo publish" seems to be different than "cargo build". I would leave running it in CI until later tho.