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. 


From the tip of your branch:

```
test=> SELECT * FROM information_schema.ak_casts;
ERROR: Cannot find the table `information_schema`.`ak_casts`
test=> SELECT * FROM information_schema.ak_overloads;
ERROR: Cannot find the table `information_schema`.`ak_overloads`
```

Classes deriving from Services are not automatically started, they still have to be bound and required (e.g. in `default-services.yaml`). 

If the ordering can't be fixed the new service needs pulled out into its own and added everywhere needed. Alternatively, making e.g. ServerSchemaTablesServiceImpl the owner of the tables.