Transition to using github secrets to store configuration for bot token, command prefix, db info, etc.

[NBurley93]

Currently the bot is configured to use a plain-text JSON file to store configuration info. This is bad for deployment pipelines, and even worse for security if it is decided to store the file persistently.

Having these as github secrets means that in order for those changes to be made, simply changing them here in github and then running a redeploy should be all that is needed to reflect those changes.

The following keys should be added:

• BOT_TOKEN
• BOT_COMMAND_PREFIX
• BOT_DB_HOST
• BOT_DB_USERNAME
• BOT_DB_PASSWORD

Once this is done, the github deployment workflow can be updated to provide those secrets when deploying the container.

Completion Criteria:

• [x] Above mentioned keys are added to project's github secrets with corresponding starting values
• [x] Github workflow for autodeploy has been updated to add these secrets with the docker-compose up command
• [x] Bot is verified as having correctly derived the values from github on deploy.

[Shadblade5]

Not sure why the current implementation doesn't work... I'll have another knack at it with a fresh mind later