Dropwizard Ingestion

### Lacks tests, but ready for review.

Changes the URIs to:
 - /v2.0/ingest/basic - multi-tenant simple metrics
 - /v2.0/ingest/aggregated - multi-tenant statsd metrics
 - /v2.0/:tenantId/ingest/basic - single-tenant simple metrics
 - /v2.0/:tenantId/ingest/aggregated - single-tenant statsd metrics

### Drop-in

You can use this as a drop-in replacement for current ingestion by specifying it in the configuration as an `INGESTION_MODULE`. You can also take the uber jar generated in blueflood-dropwizard/targets and run it as a traditional dropwizard service (just create a config modeled after the sample in blueflood-dropwizard/src/main/resources/example-ingest-config.yaml

### Gone
I decided to do away with the processing chain approach of the current ingestion. It exists as a side-effect of the way Rackspace originally ingested data. If you need to scale up, just give dropwizard more resources.

### Punted
Dropwizard takes over logging in a major way. I still need to figure out a way to basically copy the log4j configuration to the mock DW config.