Create staging + production databases for expiration notice tracking

To get the ball rolling ahead of time, we should create the production + staging databases for the expiration notice records ahead of when the code would need to go live. Around 90% of the code is written at this point, so the database tables should be in their final state at this point.

The table definition we have currently is as follows:

CREATE TABLE `ExpirationNotice`(
  id SERIAL,
  created datetime DEFAULT NULL,
  username varchar(63) NOT NULL,
  noticeType varchar(31) DEFAULT NULL,
  PRIMARY KEY(id)
);

We query on noticeType and username, so having indexes on those fields would likely be beneficial. Currently, this is just a table in it's own database locally, but I'm open to this being put into another table if that would be more appropriate. Additionally, we will need a user for each database with access in OKD and bastion, similar to our other API tables. @chills2023 let me know if you have any questions!