Database structures

[CoasterFreakDE]

relates to #10

Is your feature request related to a problem? Please describe.
To save all settings, we need a persistent storage like a database.

Describe the solution you'd like
Best option would be a database to store all data like presets, languages and more per guild

Describe alternatives you've considered
A NoSQL Database (even as flatfile e.g. json file) would be possible.

[CoasterFreakDE]

The following data should be stored for any guild:

• One - guild_id
• One - language
• Zero to Many - preset
• Zero to One - Cronjob (varchar) Automatic drops #9
• Zero to Many - Cronjob preset

---

The following data should be stored for any preset:

• One - Name
• One - Description (Used as Drop Name)
• Zero to One - Fetch Credentials / API Automatic reward fetching #8
• Zero to One - Autoreward Credentials / API Automatic rewarding #7

[CoasterFreakDE]

Credentials:

• type - varchar
• url - varchar
• method - varchar
• authorization: varchar
• format: varchar?