Hidden pk as sequence

Update the internal AIS processing to have tables with no primary key use a hidden column with a sequence. Previous this would use the hidden column with a unique ID generator. The latter has proven to be a performance bottleneck. So simplify the code by removing the unique ID generator and using a sequence instead. 

The challenge here is may pieces of code assumed the hidden column/unique id, and needed to be touched/updated to correct.  The biggest headache here were the Alter Table changes trying to ensure the hidden column, sequence, and PK were correct passed along if unchanged or removed if adding a new PK. 


The problem revolves around the (Abstract)SchemaManager and the `StorageFormatRegistry` being correctly constructed so the AISMerge process, when it checks `Table.hasMemoryTableFactory()`, which consults `Group.hasMemoryTableFactory()`, which consults StorageDescription, which consults `StorageFormatRegistry` returns correct results. 

The class isn't explicitly referenced anywhere, but is via the Guice Injector based upon the SchemaManager service being brought up successfully. This follows the pattern used by all of the other information schema table implementations. See also `BasicInfoSchemaTablesServiceImpl`, `ServerSchemaTablesServiceImpl`, `StorageSchemaTablesServiceImpl`