Some sharding code paths (such as migration commit) rely on a shutdown code to be specified in order to gracefully terminate.

The DBConnectionPool stops working when the server starts the shutdown sequence, but returns code 17382, which cannot be used to infer a shutdown.

We should make it return a ErrorCodes::ShutdownInProgress instead.