Initial Stately schema, generated code, and usage in GlobalSettings

[bhollis]

This is step 1 in adopting StatelyDB as a replacement for Postgres. StatelyDB is a new document database I've been building.

For now, StatelyDB is in private preview, so folks can't self-service set up a store or use the console, but I can manually add contributors if anyone is interested.

This PR does a few things:

1. Creates a StatelyDB schema representing all of our existing data types.
2. Generates a TypeScript client with typed objects from schema.
3. Create a client bound to our store (i.e. database), which I have already created out of band.
4. Update our Kubernetes config to pass the STATELY_CLIENT_ID and STATELY_CLIENT_SECRET auth parameters as environment variables. I've already installed these in the cluster out of band.
5. Update the platform_info route to attempt to load GlobalSettings from StatelyDB, before falling back to Postgres. This should prevent any disruption if there is a problem while making the switch. This is the only runtime interaction with StatelyDB at this point.

[bhollis]

OK, perfect. I'm currently at the point where I need to set up a test store and point the tests at that.