have setup.sh create a ~/.discord-ttl/ directory

[ayubun]

this will solve a few problems with the setup script. the first one being that there's not really a good way to tell if setup has been run yet. the second being that it keeps the client code separated from the code managed by git (since client code is updated using CURL, it does not need to be in the git repo)

[ayubun]

the separation from git will make the dev environment much easier to work with :o it should also allow for the install script to be run as a standalone (one-line CURL) without needing to clone (for clients; NOT for developers)

[ayubun]

this will probably require the #10, since it will become less intuitive to interface with the .env file with it being in a dot directory. the cli can provide a way to start the bot / update the env, but also things like trail logs, check version, update version, freeze version, downgrade maybe(?), and cleanly uninstall TTL