GEOMESA-6 Secondary Indexing (PR for comments)

Starting this PR for comments contains code from GEOMESA-169 that will be removed after PRs 107,108 are merged. I'll squash things up later.

The table format changes. Each store has a "Catalog Table" to store feature metadata then three tables per SFT:
1. Attribute Index - Inverted attribute index of simple feature values
2. Record Table - Records only (contains rows referenced by inverted index)
3. ST Index - same as before (spatiotemporal index)

Only equalTo and like queries with trailing % should hit the attr index

AccumuloDataStore is backwards compatible with the old table format (only ST with metadata) and will respect that.

Other Notes:
* Haven't updated the GeoMesa pages yet for multiple tables...that'll come in the next PR

Please comment :)
In general, I think we need to come up with a cleaner way to do this.  Would it be fair for the IQP to construct or call out to three different classes/objects here so that we can separate concerns?

Thoughts?

I'm hoping to make the Query Planner very, very easy to reason about.