Support explicit schema selection for the migration table

[pnehrer]

Add the ability to specify a table schema for the refinery history table, in case a non-default schema is required:

• refinery cli takes an optional --table-schema argument
• when a schema is provided, refinery attempts to create it, if it doesn't exist, when asserting the existence of the history table
• all table operations subsequent to this use the qualified table name so that they are performed in the correct schema

[pnehrer]

@kriswuollett apologies in advance for my unfamiliarity with the process -- how can I get this PR reviewed? Thank you in advance!

[jxs]

Hi, thanks for the interest and apologies for the delay in reviewing!
I am curious, can you elaborate on why you need to define an explicit schema for the migration table?

[pnehrer]

@jxs certainly -- in our application we use a single database with multiple schemas, roughly one for each micro-service or domain. Each micro-service/domain manages its own tables and migrations. Thus, the migration table must be in the respective schema; otherwise conflicts arise among them. Thanks!