Before this change, the goose migrations "just worked", as long as the postgres searchPath was set to the correct schema.
With the new change, the existence check looks in the "Public" schema, where it is not present, and then fails when trying to create the table in the default schema (according to searchPath).

While we might get around this, by prefixing the migration table name with the schema, it then requires the migration to be schema aware, where it didn't need to be before.