Hot-Reload dependencies and enforce order of operations

[aaronburtle]

DAB has a number of objects that are instantiated during startup, using values from the config, which are used to determine how to handle requests correctly. During a Hot-Reload, it is not enough to simply update the RuntimConfig objects, these objects that were instantiated on startup also need to be refreshed. These include the following classes:

QueryManagerFactory
MetadataProviderFactory
QueryEngineFactory
MutationEngineFactory
QueryExecutor
MsSqlQueryExecutor
MySqlQueryExecutor
PostgreSqlQueryExecutor
OpenApiDocumentor

And because some of these classes depend on the others, the order above must be enforced as the order in which the refreshing of the objects takes part. Since these classes are registered as singletons, we know that but a single instance of each object is used by DAB, and so refreshing that object will handle the refreshing of the dependencies for the entire service.