Move dispatcher into its own program

[Douile]

This is required before implementing #67

What is this branch

This branch is moving the dispatcher component (part that queries game server state, generates a status message, and
sends that message to discord), into its own seperate program from the main bot.

The reasons for doing so are as follows:

• Simplify code-base
• Allow for rewriting the bot
  • Dispatching requires node-gamedig, a javascript library, so by seperating this out we can rewrite the main bot part
    in any language we like
• Allow for running N dispatchers
  • More easily spread the load of querying from multiple servers without needing a discord websocket connected

TODO:

Required

Scheduler

• Store metadata on status (or in seperate table)
  • last updated time
  • updated by (dispatcher ID)
• Store client errors
  • error code
  • error message
  • dispatcher ID
  • (server offline is not an error)
• Use TLS for postgres

Dispatcher

• Send ID to scheduler
  • Login packet?
    • Scheduler can have allowlist for IP - ID + secret
• Better transport medium
  • encrypted
  • more efficient that JSON: protobuf, CBOR
• Implement local IP blocklist (in runtime indepedent way)
• Get working on different runtimes
  • Deno (should work now, missing net:blocklist)
  • Bun (requires - Implement dgram oven-sh/bun#1630)
• Make a common query library to be used by both the bot and dispatcher

Docs

• Update docs

Nice to have

Scheduler

• Don't use arcs for objects that live forever
• Pipeline database
• Make code less of a mess

Bot

• Finish rust rewrite

Docs

• Architecture diagram