feat: add supabase

[ViorelMocanu]

📚 Description

This PR...

🔗 Linked issue(s)

Fixes #160, fixes #12, fixes #76, fixes #100

❓ Type of change

• [ ] 🐞 Bug fix (non-breaking change which fixes an issue)
• [x] 📖 Content update (text or image-related updates)
• [ ] 🖼️ Design update (UI design and static template related change)
• [x] 🆕 New page (addition or major edit for an existing page layout)
• [ ] 📓 Documentation update (improvements or additions to documentation)
• [x] 👌 Enhancement (improving an existing functionality, like performance)
• [x] ✨ New feature (a non-breaking change that adds functionality)
• [x] 🛠️ Operational update (changes to configuration, CI/CD, procedures, etc.)
• [ ] 🛡️ Security update (a fix or update required to alleviate a cyber security issue)
• [ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to not work as expected)

📄 Changelog

• ...

✅ Checklist

• [ ] My code follows the style guidelines of this project
• [ ] I have performed a self-review of my code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] My changes generate no new warnings or errors
• [ ] I have manually tested the newly added functionality with no discernable errors
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
digital-resources	❌ Failed (Inspect)			Jan 22, 2024 11:23am

[cloudflare-workers-and-pages[bot]]

Deploying with    Cloudflare Pages

Latest commit:	113fd40
Status:	🚫  Build failed.

View logs

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	Secret	Commit	Filename
9343760	PostgreSQL Credentials	113fd40c012a7d38c1925f9eedb86c1234251604	.env.local	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>