Create a table for digital bookplate batches

[shelleydoljack]

The table will be used to keep track of when users trigger the add 979 field DAG manually through the UI. Previously, this table would contain the following information: submitted date, created by, report email, batch type (add or delete), bookplate druid, filename, ckey count, completed date.

We also presented the user with batches in the queue (not yet processed). It showed the same information as the completed batches, driven by a query where completed_date is null. The bookplate batches table could have a separate "processed" or "completed" column if that would make presenting completed/in queue information easier.

[shelleydoljack]

As an airflow admin user, I can see the status of the dag runs. As a user who has access to upload files to the UI, I do not have the ability to view the DAGs and the statuses of their runs. Creating a table to keep track of bookplate batches (and the views) is a "nice to have" and is not necessary for the work cycle. This could be prioritzed once more of the dags are completed.

[shelleydoljack]

This table was used to figure out what needed to be processed when the script to add 979 fields ran on a schedule outside of business hours. Since the DAG to add 979 will run whenever it is triggered, then we don't need to keep track of queued/processed. I'm going to move this to the Icebox since it is not required for the work cylce.