Make controller API consistent

There are a few class of issues with the API today
* Config Field name (eg: tablename inside table config sometimes has type - sometimes not)
* get and put json payloads: json retrieved from get API doesn’t always work with PUT.

Start at the controller API entry points and inventory the table configuration fields, especially tablename and its type, alongside the GET and PUT JSON payload handling. Compare the schemas and round-trip behavior; done means configuration field definitions are consistent and JSON returned by GET can be submitted through PUT.

Written by the indexing model from the issue text.