DDL - DB Migration with @History and Postgres - views need to be dropped early to support migration changes

Postgres is strict with respect to changes that invalidate views (it prevents them) so this means that with changes to entities with @History we need to drop the relevant history views first before we made type changes etc to the columns.

In summary: We need to detect and drop dependent history views before applying the columns changes.
