Upgrade configuration to use a toml file over .env.server #3420
Description
Another configuration update? Didn't we just stop using yaml?!
As apparent while working on botstrap and updating the contributing guide, it is very confusing how to configure specific variables for the environment without having to configure a LOT of manual values. Some people additionally don't want to manually configure their bot or have a large test server where they don't want to run botstrap.
A toml file configuration format should be supported, and .env.server should be deprecated.
To help with this migration, we can add a cli to botstrap to add a command to migrate the .env.server file to a new toml file.
The question is, how do we best implement configuration and configuration hiearchy. I am opposed to having a tool such as botstrap write to a configuration file I may have changed for a reason, and I enjoy how it currently writes to .env.server (which I think should have been named .env.autogen but I digress). If we change configuration to a toml file, we would still need to support environment variables, for bot token and other such variables. A migration tool is quite important, as well.