Refactor: Move into proper project config

[JacobCoffee]

Summary

After some testing it seems we can do what we want.

We should clean things up to start building upon.

• Build from an inherited base class instead of def run
• Other "standard" bot design patterns
• Update web/ against the latest fullstack reference
• Proper logging to be shared between the two?

Basic Example

something like this, I think

➜ ntp bytestructexample && mkdir -p src/{web/{lib,domain},bot/{ext},lib/{db,log}} && tree
  bytestructexample
 └─  src
    ├─  bot
    │  └─  {ext}
    ├─  lib
    │  ├─  log
    │  └─  db
    └─  web
       ├─  domain
       └─  lib

Drawbacks and Impact

No response

Unresolved questions

No response

[JacobCoffee]

Another idea architecturally would be to just have the bot made API calls to a Litestar API that can be scaled as needed. This way we could showcase Litestar in action, explore different design patterns, scale better, etc.

[JacobCoffee]

We should avoid any inter-domain dependencies in case we separated from the monorepo pattern.