[Solution] Turn `Draupnir` repository into a monorepo

[Gnuxie]

• Create a branch monorepo-dev that we can merge each step into that is distinct from main
  • Move src into apps/draupnir
  • Update build artifacts, ci workflows, etc work with the new setup
  • Only proceed when stable
• Copy @gnuxie/tsconfig into packages/tsconfig
  • make sure apps/draupnir now depends on the tsconfig package.
• Import each package one by one from the bottom up ie closest to draupnir first changing over to the correct tsconfig.
• Finish up with moving typescript-result into the repo too.
• Merge into main.

[Gnuxie]

we probably need a shim for when apps/draupnir/lib gets built and everyone still expects lib/index.js

otherwise we will need to v3.0.0 draupnir.

Progress so far has been fine. Up next is just to install dev deps at the root and keep adding more packages...

[Gnuxie]

taking \"apps/**/{src,test}/**/*.{ts,tsx}\" out of lint for now since we're not including apps in the tsconfig yet

[Gnuxie]

as we release packages we will have to manually undo the temprarily file:../ links we've setup to boostrap the monorepo

[Gnuxie]

package local prepare scripts are hell and should be removed because they resolve binaries from the package node_modules instead of from the root... They all need deleting

[Gnuxie]

calling it quits for today... mps-interface-adaptor's interface-manager dependency needs fixing as currently it's not being met for whatever reason

edit: This was against caused by silly prepare scripts rm -rf ing dist and then using wrong version of typescript aaaaa

[Gnuxie]

So we were doing really well and we were about to integrate apps/draupnir when i stopped to check how to manage tests... well it turns out that eslint is stupid and only checks the nearest tsconfig.json with projectService unless we want to use a bunch of legacy options... unless i can find a way to configure it.

[Gnuxie]

Ok we figured something out by giving eslint its own config. We're ready to finally add Draupnir :3

[Gnuxie]

The matrix-bot-sdk alias is causing us issues now... because we switched to npm and it has different behaviour there with regards to yarn.

[Gnuxie]

solved. Now we're just trundling through some type comaptibility issues of my own making when i decided to upgrade typescript at the same time 👍 but yeah.

Essentially there's a few places where we really need a top type for e.g. CommandDescription ie AnyCommandDescription but at the same time we need to be able to call the executor in internal code. The way i'm thinking of solving it is just to keep the registration api generic but then internally we just cast things behind a veil of utility functions.

[Gnuxie]

Trundled through various typescript failings today on draupnir specifically. Now we are working through the eslint findings.

[Gnuxie]

i also deleted the appservice's widget api that has been unused for 3 years because it was pretty much all written in a way that is inappropriate in modern typescript. And we would need to rewrite it anyway to keep it (but it won't be used).

[Gnuxie]

yeah we see some shit like that and then realise our config file does similar shite