Previously, the declarative schema changer when adding a column with a unique index did not generate the
appropriate error when an unsupported type was encountered. As a result, we would wait till execution and
require a rollback for this issue to be detected.

Jira issue: CRDB-17514