Add server boot scripts to install and/or update SQL views

[preston]

This is potentially challenging due to race conditions during the boot process. When CQL Studio Server starts up, it will need environment variable configuration options for the database connection string, and then be able to automatically connect, detect if views are installed, and install and/or forward migrated them, all automatically and with no user intervention.

[preston]

@danielhmendoza01 Do you have some instructions on the best way to use wait-for-it? The parent epic of this ticket for CQL Studio will require CQL Studio Server to wait for HAPI's PostgreSQL database to spin up, and then run some initialization scripts. CQL Studio Server is extremely lightweight and fast to start, so it's very likely to have race conditions with the Postgres image boot.

[danielhmendoza01]

Where is the Github and/or docker file for the CQL Studio Server? I am guessing you do not want to do a health check so I’m thinking the cleanest way to handle the startup race condition is to add a small entrypoint script that waits for Postgres (and possibly HAPI) to be ready. @preston

[preston]

@danielhmendoza01 We had a meeting about this last week and are going to go in a slightly different direction. Rather than do anything at first boot, we are going to install generated SQL views dynamically on demand via the UI. But the bottom line is that introducing boot scripts fortunately won't be required.