Explore using config to unhardwire list of things loaded on install

The current install system uses a number of mechanisms to prepare for installation. What if we were to use the configuration system to handle this stage of the process?

Could we simplify the methods that are used early in the process and reduce the number of dependencies that the system requires by doing this?

This seems like an excellent adventure to take.

@TODO
Write code to pull settings from a configuration file to preload Drupal so that dependencies on the DB are satisfied.
Look to eliminate or simply functions that currently require a DB present in the early stages of a Drupal installation.