Investigate creating an Ace Archive monorepo

[frawleykid]

Currently, the project is spread across over a dozen repos, which presents some challenges:

• Things like CI pipelines, just recipes, editor configs, linter configs, etc. need to be duplicated between repos, which is tedious (see Standardize linter, formatter, and compiler configs across repos #4, Run linters, formatters, and type checkers in CI, across all repos #5).
• One piece of work may touch several repos, which complicates development and PR review.
• Documentation is scattered in many different places (see Centralize developer documentation in one place #26).

For this ticket, investigate what it would look like to create an Ace Archive monorepo, moving some or all of the services under this repo. Some repos may make sense to keep separate, but the various Cloudflare Workers are likely all good candidates for the monorepo.

Nothing needs to actually be migrated for this ticket; consider it a good opportunity to learn about the architecture of Ace Archive and how each of the different services and repos interact. The architecture diagram might be useful.