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 :)
Should we at least throw an exception if this case statement fails?  We may want to open another ticket to handle this more broadly.  I think we've covered some of the most frequent cases here, but there is no constraint (of which I am aware) that `PropertyIsEqualTo` filters must have exactly one `PropertyName` child and one `Literal` child.