Allow running cli commands without db connection

[spencewenski]

Creating the app context requires connecting to the db (if a db feature is enabled). If no db is running, the cli will not run. We have a couple options:

1. Can we create the db connection pool (sql, redis, etc) without needing for it to be able to actually connect to the db?
2. If (1) is not possible, we can add a method to the RunCommand trait that runs right after the app config is parsed (and tracing is initialized) and before the app context is created.

[spencewenski]

This can also impact commands implemented by services, eg, the openapi command. It would be good if the openapi command could be run without needing to start the db

[spencewenski]

Can we create the db connection pool (sql, redis, etc) without needing for it to be able to actually connect to the db?

I don't think this is currently possible with seaorm, but I think it is with sqlx, so we may be able to submit a PR to seaorm to enable this behavior.

[spencewenski]

Opened a PR on SEA ORM: SeaQL/sea-orm#2268

[spencewenski]

For redis/sidekiq, we need to move the "stale cleanup" behavior out of the "build" method so it runs after the service is built and after the "handle cli" method is run against the services.

[spencewenski]

This should be a quick fix once SeaQL/sea-orm#2268 is merged.

[spencewenski]

The seaorm team is taking a while to look at the proposed pr above.

An alternative could be to use a OnceLock to lazy init the db connection?

[spencewenski]

Hmm, the problem with OnceLock is the db connection creation can return an error, so we would need to add a layer of checks everywhere the db connection is requested.