adding a column to an enum table puts the metadata into inconsistent state

Repro:
1. Create an enum table with `id` and `description`.
2. Try adding a new column to it.

The console says: `Adding column failed due to inconsistent metadata`. However, the column does get added but console forever shows the following error on the table page.


Not sure if it's the intentional behaviour, but I felt like actions on console shouldn't create any inconsistent metadata.

Reproduce the console workflow by creating an enum table with id and description, then adding a column. Trace the enum-table column-addition and metadata handling entry points; done means the column is added without the inconsistent-metadata error and the table page remains usable.

Written by the indexing model from the issue text.