Migrate the codebase to use Supabase instead of MySQL

[sweep-ai]

Description

This PR migrates the codebase from MySQL to Supabase as the database provider. It includes changes to the database configuration, ORM models, service layer, and test data helper. The goal is to ensure that the application continues to function as expected after the migration.

Summary of Changes

• Updated the database configuration in app/config.py to connect to Supabase instead of MySQL.
• Modified the ORM models in app/entities/orm/orm_model.py to work with Supabase.
• Updated the service layer in app/api/endpoints/users/users_service.py to use Supabase's API for database operations.
• Rewrote the test data helper in tests/data_helper.py to work with Supabase.
• Removed the Docker configuration for the database in db/docker-compose.yml.
• Removed the MySQL initialization script in db/init/10.my_db.sql.
• Removed the MySQL configuration file in db/my.cnf.

Please review the changes and ensure that the application functions correctly with Supabase as the database provider.

Fixes #5.

---

To checkout this PR branch, run the following command in your terminal:

git checkout sweep/migrate-to-supabase

---

🎉 Latest improvements to Sweep:

• Getting Sweep to run linters before committing! Check out Sweep Sandbox Configs to set it up.
• Added support for self-hosting! Check out Self-hosting Sweep to get started.
• [Self Hosting] Multiple options to compute vector embeddings, configure your .env file using VECTOR_EMBEDDING_SOURCE

---

💡 To get Sweep to edit this pull request, you can:

• Leave a comment below to get Sweep to edit the entire PR
• Leave a comment in the code will only modify the file
• Edit the original issue to get Sweep to recreate the PR from scratch