Add GeoServer subpanel to support configuring visibility options

[rwgdrummer]

Current visibility options are determined by a GEOWAVE_VISIBILITY attribute of a feature. Each layer should define it's own visibility criteria.

The visibility metadata should be maintained in zookeeper. The visibility metadata should be associated with each adapter (typename). The metadata includes the attribute name and the parser. Currently, there is only one:JsonDefinitionColumnVisibilityManagement. These options are provided to the FeatureDataAdaptor in its constructor as called by GeoWaveGTDataStore#createSchema. Somehow, the GeoWaveGTDataStore must compile and maintain the metadata. The visibility page access the data though the data store.

Of note: each GT Data Store instance is associated with a workspace and has its own set of associated layers. At the moment, namespace issues can be resolved having layers have unique names. However, the developer should consider the possibility that two data store instances have the layers with same name. I do not think is possible or realistic. Thus, metadata could be simply indexed by typeName.

[chrisbennight]

Is this talking about the visibility for metadata values (indexes, featurestypes), the visibility for secondary index type stuff, or visibilitiy handling "extensions" for WFS-T, or something else?

If it's one of the former do #70 or #71 answer any of the questions?

[rwgdrummer]

Need to use panel to set the the attributes that are indexed in a temporal index. This is checkbox that results in setting meta-data associated with feature attributes. For range, the meta data names are 'start' and 'end'. For a simple time element, the meta name is 'time'. The value is either true or false.