If we were to drop a unique secondary index cascade and this unique index backed a FK constraint
in the referenced table, we should drop the index and the FK constraint. Presently, the declarative schema
changer just fallback. Now that we have supported dropping FK constraint, we should be able to support
this in the declarative schema changer.

Jira issue: CRDB-24297