Configure automatic gitea boot from configuration file

[uwardlaw]

• Gitea needs to start up automatically without requiring button pressing
• The data base needs to initialize without the current splash page
• An admin user needs to start up automatically with an ssh key

[uwardlaw]

Created the setupGitea.py and got far enough to make tokens.

ROUS is a private repository, and therefore requires a deploy key on Control. Then, the API calls need to be made to setup the mirror repository

[uwardlaw]

• Setting the token and then looking it up again because Gitea (rightfully) does not pull the full token when searched. This is different from Ansible.
• Was able to call API, but a private git (ROUS) requires SSH authentication. Knew this, but not confident in how to get the key in there

[uwardlaw]

• Gitea does not support SSH merges natively. Migrate from SSH go-gitea/gitea#1635
• Gitea stores repos a /data/git/repositories/

[uwardlaw]

The #1 is as subset of this issue.

[uwardlaw]

• Instead of pulling ROUS from Github, we will pull down a local copy (this is good for dev anyway) and then restart.sh will copy it into control-services/data/gitea/git/
• The repo will only updated when the copy on the host updates
• Need to create organization so the added repo can have an owner before users are created
• Need import path is file:///data/git/rous
• This works well, but because the config user is the owner of the repo, the config user can't be deleted anymore
• The config user will now need to be a real user that stays (instead of being deleted after API calls)
• Started adding password ask / check support to setupGitea.py
• Code mostly works, but not extensively tested for errors yet

[uwardlaw]

• Completed the login functionality
• Started handling dict and list separately in getIDFromName
• Script completes on run after clean.sh and after multiple runs
• Still need setupGitea.sh errors if a token of the name configurationToken is still valid #9 at a later date