This PR proposes migrating our shared code structure to follow a more traditional monorepo organization. This essentially follows the guidelines from Turborepo, though this PR does not go so far as to actually use it. See Orval for a codebase that uses Turbo.

Namely, there is a new top level packages folder that houses isolated modules of shared/reusable code. Each of these will have their own dependencies, scripts, versions, test suites and will import from each other as you would import from any other package. This PR begins this process by migrating some web-common code to three packages: utils, events and actions.

I think there are number of benefits to this structure (and Turbo), though I would be lying if I said I wasn't mostly motivated by shortening our exceedingly long import paths. 🤷

A follow up PR would move our web-local, web-admin and web-auth apps into an apps folder, at which point I think we should rename them to developer, cloud and auth.

This is an open discussion, but I anticipate creating the following additional packages based on our existing code: ui, state, formatting, query, icons, time, features, metrics and other packages for shared configuration.

This PR also upgrades eslint to v9.