Fix: #44
Fix: #38

IMPORTANT: Please do not create a Pull Request without creating an issue first.

Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.

🗓 Changes

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Please provide enough information so that others can review your pull request:

🧬 Details

Explain the details for making this change. What existing problem does the pull request solve?

With this update, we have transformed each functionality into a separate plugin that can be enabled or disabled on a per-guild basis. As new features are added, they will also be implemented as individual plugins. This provides greater flexibility and customization options for our users.

• Moves from MongoDB -> Supabase:
  - All functionalities are now plugins and they can be enabled/disabled per guild basis.
  - When the bot is started, it will fetch and insert all guilds, plugins & configurations to the database.
  - New Schema for Guilds
  - New Schema for Plugins
  - New Schema for Configurations
  • Adds /ask command for chat GPT, only works with premium guilds (this concept is for know guilds where we can try a given functionality and runing with the costs) but each guild can have they own API key and use it freealy.
  • Adds /plugins command to configure the bot for each guild.
  • Moves from npm to yarn.

Checkboxes:

• I ran npm run lint and there were no errors
• I ran npm run format and there were no errors