Run create_superuser to create super user on application's start

[pbanaszkiewicz]

This fixes #2310.

[pbanaszkiewicz]

The idea here is to run create_superuser command when the container starts, so that admin user is created and we get to know their password.

I can see the CodeQL checks are complaining, so maybe I'll drop the password printing and accept the fact that new installation will have admin:admin superuser.

[pbanaszkiewicz]

Added tests to make sure the command behaves like I want.

It will create the superuser account only if one doesn't exist. The existing superuser account will not be changed.

When moving this code to production, we can easily create account for user admin and disable it; this way the script doesn't do any harm.

[pbanaszkiewicz]

Conflict resolved. @elichad Can you review this PR?

[elichad]

When moving this code to production, we can easily create account for user admin and disable it; this way the script doesn't do any harm.

Is it worth creating that user now so we don't forget about it later?

[elichad]

Also, I haven't looked through the new CI/CD setup yet - is the database recreated from scratch every time the test server is re-deployed, or does it persist?

[pbanaszkiewicz]

@elichad

Is it worth creating that user now so we don't forget about it later?

Good idea. I have just created this account on production server and disabled its permissions and access.
CC @maneesha @froggleston

Also, I haven't looked through the new CI/CD setup yet - is the database recreated from scratch every time the test server is re-deployed, or does it persist?

No, database persists. It is treated as a completely separate service from the application.