We probably wouldn't combine multiple configuration files, but come up with a way to merge configuration objects instead.

A single text file containing configuration settings and a separate java class per module/package/whatever defining constants and default values.  Assuming we keep the main configuration as a singleton, we just need to come up with a way to get new defaults into it.

```java
// load all properties from blueflood.config
Configuration config = new Configuration();
// or Configuration.getInstance();
config.init();
// or config.init(some_url)
...
ConfigA configA = new ConfigA(Configuration.getInstance());
String aa = configA.getStringProperty(ConfigA.SOME_KEY);

ConfigB configB = new ConfigB(Configuration.getInstance());
String bb = config.getSomeAwesomeStringWithARealName();

// wipe out B and populate with entirely new data.
configB.init(new java.util.URL("file:///etc/bf/some_special_config.properties"));
```

I feel strongly that having multiple configuration files would be a mistake, but this kind of API wouldn't preclude that.

Reworking the configuration process is beyond the scope of this PR though.  It's already on the kind of big.