refactor: ✨ Create TS monorepo structure

[timbrinded]

What does it do?

Structures the TS packges of this repo so they share package versions and tooling. This will simplify releases by reducing the amount of steps.

What value does it bring to the blockchain users?

More frequent and reliable NPM packages

[github-actions]

WASM runtime size check:

Compared to target branch

Moonbase runtime: 2260 KB (no changes) ✅

Moonbeam runtime: 2248 KB (no changes) ✅

Moonriver runtime: 2240 KB (no changes) ✅

Compared to latest release (runtime-3400)

Moonbase runtime: 2260 KB (+232 KB compared to latest release) ⚠️

Moonbeam runtime: 2248 KB (+236 KB compared to latest release) ⚠️

Moonriver runtime: 2240 KB (+228 KB compared to latest release) ⚠️

[github-actions]

Coverage Report

@@                 Coverage Diff                 @@
##           master   feat/ts-monorepo     +/-   ##
===================================================
  Coverage   74.58%             74.58%   0.00%     
  Files         375                375             
  Lines       95682              95682             
===================================================
  Hits        71359              71359             
  Misses      24323              24323             

Files Changed	Coverage

Coverage generated Wed Dec 11 09:37:57 UTC 2024

[RomarQ]

I think we should be able improve the reliability of the packages in some other way, having generated code committed is usually a bad practice.

Cons:

• This will make reviews more complicated, a good example will be polkadot-sdk dependency updates, which will produce a huge diff;
• Unnecessary merge conflicts;
• Large commits will significantly inflate the size of the repo, which will make cloning, fetching slower.

Pros:

• Detecting metadata changes in the PR that changes it.
• Reduces the amount of steps in some workflows.

[RomarQ]

Overall looks good, but having dependencies using any version can be unstable. It will be fine if we no longer plan to publish the packages to npm

[timbrinded]

It's not using any dep version, it's fixed in the top level.

We use * so that ALL sub projects use the SAME version to stop inconsistencies of the past from breaking publish