move all blueflood http stuff into its own maven module
Use interfaces to remove cyclical dependency on blueflood-http in bf-core
Move missed test classes into blueflood-http module
Update http integration tests to use new interface methods
Remove empty strings and spaces from configuration arrays
Shutdown the jvm if a loading an ingestion or query module fails
Add necessary maven plugins to get integration tests working
Create processor chain only after setting context property
Ensure ScheduleContext's update method is actually called during ingestion
add resources required by integration tests
update pom with license and testing deps
Changes suggested in PR
refactor configuration to get defaults from properties file. first step to be more module friendly
Refactor configuration for modularity

- Use singleton pattern instead of static methods in Configuration so it
  can be subclassed.
- Split helper functions and module-specific settings (namely the
  default config values) into separate classes: Configuration and
  CoreConfiguration.
- Move default config values into a properties file kept in the
  resources dir.
Use new configuration pattern in blueflood-http
keep service implementations under c.r.blueflood.service namespace
Use new config pattern in blueflood-udp

For now just use the CoreConfiguration singleton. Refactor to use its
own configuration singleton in another PR.
add license headers
add license header
Use new config pattern in blueflood-udp - missed one