Migration fails when using database schema

[jemidi]

When using a database with a schema the table created by 67_api_keys.up.sql will be schema.api_keys.
The subsequent changeset in file 68_api_key_last_used_at.up.sql will hence fail as it - unlike other changesets - references the public namespace directly:

ERROR: relation "public.api_keys" does not exist [Failed SQL: (0) ALTER TABLE public.api_keys
ADD COLUMN last_used_at DATE]