🏗️ Using normalized package architecture

[Sigmanificient]

This pr changes the current code base to follow a standard python package architecture.

Main changes

• Added setup config for local installation
• Moved config & data files to a dedicated vars directory
• Improved python code and structure
• Moved run to a package entry point
• Updated documentation
• Added a Makefile for easier GNU/Linux setup

[drawbu]

Why deleting all the -> None ?

[drawbu]

Why is there an empty file drawbot/cogs/__init__.py

[drawbu]

Why deleting this?

[Sigmanificient]

I put a config.json.example file people can directly copy and rename. Since the content is within the example file, it isn't much useful in the readme, i believe

Plus having a example file within the vars folder should avoid people to try creating a config.json at another locater, i hope

[drawbu]

Yep it will be easier for some, but harder for a majority. People using this bot are in majority beginners, so we need to make this accessible. I'm just gonna adding it back, and we'll have both available

[Sigmanificient]

Sure

[drawbu]

Just put this into the utils/ folder

[Sigmanificient]

Sound fair enough, could move it when i'll be at home

[Sigmanificient]

Why is there an empty file drawbot/cogs/__init__.py

This insure cogs to be a sub-package part of the whole drawbot package and thus being included in the installation process

[drawbu]

Yeah, but why leave it empty?

[Sigmanificient]

Yeah, but why leave it empty?

There is nothing to really put in that init file since discord will use dynamic import for cogs.

I believe that is more a design problem from the lib, as it would has been smarter to handle object, like the nextcord fork did, cause less "python weirdness" and a overall better code structure & logic.