Refactor create superuser

[rragundez]

IMPORTANT: #229 must be merged first

The reasoning behind creating such functionality of a script to create a super is 2 fold

• startup configuration where there is no super user
• super users of the application for whatever reason have been compromised or no super user left.

Because of this, this functionality should be treated with caution as it provides the way create a super user while bypassing any application auth measures, and since there are only 2 scenarios were they are needed is OK to be very strict. For example:

• Running such script has to be very explicit, therefore running it automatically as a service is not recommended. On top that manual work (commenting and uncommenting the service from the docker file has to be done depending on the desired behaviour)
• Providing the option to use the script to create any number of super users should not be allowed.
• Strict control over the version of the script should be inplace. This PR introduces a checksum verification which is not bullet proof but adds a layer of security to modifying the script.
• Script should try to follow logic already created in the application such that measures, controls, and DB schemas are respected.
• Better logging at the start of the script for auditing
• CLear indication messages on when and how to run this file