backend: Attempts to use Configuration table before running the create table statement

[frozenfrank]

Recent changes have created a new table, but other changes attempt to put default values into the table before the create table statements are run. This causes an issue when the table doesn't already exist.

For an individual, it's pretty straight forward to just run the create table statement, but the system should be able to do it automatically.

See the screenshot below:

For reference, here is the create table statement:

CREATE TABLE IF NOT EXISTS `configuration` (
        `config_key` VARCHAR(50) NOT NULL,
        `value` TEXT NOT NULL,
        PRIMARY KEY (`config_key`)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci

[frozenfrank]

@19mdavenport Can you help with this one?

[19mdavenport]

resolved by #352