Add mismatched sequence size check

[hlascelles]

In Postgres, sequences can be of different sizes, for example, integer and bigint. There is essentially no reason ever to have a sequence that will have a smaller size than the primary key that it is vending IDs for.

This PR adds a check to make sure that the sequence type matches that of the primary key ID column. Without it, a user may have a database column, which is bigint, and a sequence which is integer and will overflow unexpectedly.

Note here the AS integer line.

Bad:

CREATE SEQUENCE public.id_seq
    AS integer
    START WITH 1
    INCREMENT BY 1
    NO MINVALUE

Good:

CREATE SEQUENCE public.id_seq
    START WITH 1
    INCREMENT BY 1
    NO MINVALUE