fix: Updated run-platform to create schema for new users

[chandrasekharan-zipstack]

What

• Fix in run-platform.sh to create DB schema
• Fix in migrate-to-v2.sh to allow talking to DB / redis in containers
• Updated ENTRYPOINT to CMD in backend's Dockerfile, to allow invoking the necessary schema creation command
• Renamed and moved the schema creation / drop commands to utils app

Why

• Schema creation has to be done explicitly once as part of the v2 changes, previously this was done by django-tenant and the public schema would be present by default
• As a result new users faced this issue

How

• For first time users, schema creation handled with command run on backend container
• For existing users, they will have to read the release notes and manually run backend/migrating/v2/migrate-to-v2.sh to perform the schema creation and subsequent migration

Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)

• Yes, since it touches the backend Dockerfile and some scripts used by OSS users - it is possible

Database Migrations

• Might run when these scripts are invoked

Related Issues or PRs

• Script to run v2 migration commands #791
• Issue from support channel

Notes on Testing

• Removed /etc/hosts entries to mimic the average OSS user to reproduce the same issues and worked on unblocking myself

Screenshots Old

• To be used by new users, ran with trace option
  

• Migration script (to be used by existing users)
  

Screenshots after addressing comments

• Schema creation handled through entrypoint script
  

Checklist

I have read and understood the Contribution Guidelines.

[hari-kuriakose]

@chandrasekharan-zipstack Let's also move scripts/ to docker/scripts/ along with this.

[chandrasekharan-zipstack]

@chandrasekharan-zipstack Let's also move scripts/ to docker/scripts/ along with this.

@hari-kuriakose I've addressed it in this PR - can we let these be separate changes? Will resolve any conflicts accordingly

[jaseemjaskp]

LGTM

[github-actions]

filepath	function	$$\textcolor{#23d18b}{\tt{passed}}$$	SUBTOTAL
$$\textcolor{#23d18b}{\tt{worker/src/unstract/worker/clients/test\_docker.py}}$$	$$\textcolor{#23d18b}{\tt{test\_logs}}$$	$$\textcolor{#23d18b}{\tt{1}}$$	$$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{worker/src/unstract/worker/clients/test\_docker.py}}$$	$$\textcolor{#23d18b}{\tt{test\_cleanup}}$$	$$\textcolor{#23d18b}{\tt{1}}$$	$$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{worker/src/unstract/worker/clients/test\_docker.py}}$$	$$\textcolor{#23d18b}{\tt{test\_cleanup\_skip}}$$	$$\textcolor{#23d18b}{\tt{1}}$$	$$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{worker/src/unstract/worker/clients/test\_docker.py}}$$	$$\textcolor{#23d18b}{\tt{test\_client\_init}}$$	$$\textcolor{#23d18b}{\tt{1}}$$	$$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{worker/src/unstract/worker/clients/test\_docker.py}}$$	$$\textcolor{#23d18b}{\tt{test\_get\_image\_exists}}$$	$$\textcolor{#23d18b}{\tt{1}}$$	$$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{worker/src/unstract/worker/clients/test\_docker.py}}$$	$$\textcolor{#23d18b}{\tt{test\_get\_image}}$$	$$\textcolor{#23d18b}{\tt{1}}$$	$$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{worker/src/unstract/worker/clients/test\_docker.py}}$$	$$\textcolor{#23d18b}{\tt{test\_get\_container\_run\_config}}$$	$$\textcolor{#23d18b}{\tt{1}}$$	$$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{worker/src/unstract/worker/clients/test\_docker.py}}$$	$$\textcolor{#23d18b}{\tt{test\_get\_container\_run\_config\_without\_mount}}$$	$$\textcolor{#23d18b}{\tt{1}}$$	$$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{worker/src/unstract/worker/clients/test\_docker.py}}$$	$$\textcolor{#23d18b}{\tt{test\_run\_container}}$$	$$\textcolor{#23d18b}{\tt{1}}$$	$$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{TOTAL}}$$		$$\textcolor{#23d18b}{\tt{9}}$$	$$\textcolor{#23d18b}{\tt{9}}$$

[sonarcloud]

Quality Gate failed

Failed conditions
2 Security Hotspots

See analysis details on SonarCloud

[hari-kuriakose]

@chandrasekharan-zipstack LGTM overall

[hari-kuriakose]

Can take care of the Django management commands security hotspots separately.