Feat/google calendar

[SageBoots]

Pull Request

Description:

Added third party integration with google calendar for event rsvps

Related Issues:

[Reference any related issues or documents.]

Type of Change:

• [ ] Bug Fix
• [x] New Feature
• [x] Enhancement
• [ ] Refactoring
• [ ] Documentation Update

Checklist:

• [x] My code follows the coding standards of this project.
• [x] I have performed a self-review of my code.
• [ ] I have added/updated relevant documentation.
• [ ] My changes generate no new warnings or errors.
• [x] I have tested my changes.

Reviewers:

• @Mathenda

Testing Instructions:

• Sign in using a google account
• Rsvp for an event
• Check Google Calendar using event date and time

Screenshots (if applicable):

[Add screenshots to help reviewers understand the changes visually.]

Additional Notes:

[Any additional information that may be helpful for reviewers.]

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 39.29%. Comparing base (cb3e725) to head (d1b0e77). Report is 12 commits behind head on develop.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## develop #182 +/- ## ======================================== Coverage 39.29% 39.29% ======================================== Files 85 85 Lines 313 313 Branches 15 15 ======================================== Hits 123 123 Misses 190 190 ``` | [Flag](https://app.codecov.io/gh/COS301-SE-2024/Events-System/pull/182/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=COS301-SE-2024) | Coverage Δ | | |---|---|---| | [](https://app.codecov.io/gh/COS301-SE-2024/Events-System/pull/182/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=COS301-SE-2024) | `39.29% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=COS301-SE-2024#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

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

Deploying events-system with    Cloudflare Pages

Latest commit:	d1b0e77
Status:	✅  Deploy successful!
Preview URL:	https://3826eb4c.events-system.pages.dev
Branch Preview URL:	https://feat-googlecalendar.events-system.pages.dev

View logs

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 4 secrets 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 secrets in your pull request

| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [13861047](https://dashboard.gitguardian.com/workspace/301252/incidents/13861047?occurrence=166140957) | Triggered | Generic High Entropy Secret | 92a577bd4e7b64860b2fff7991e605c3903050f5 | .npmrc | [View secret](https://github.com/COS301-SE-2024/Events-System/commit/92a577bd4e7b64860b2fff7991e605c3903050f5#diff-e813096d69c49812e40e00be9ac8fa14d77f0ec1f97ab4c45cb096b3bedd35deR2) | | [13861048](https://dashboard.gitguardian.com/workspace/301252/incidents/13861048?occurrence=166140956) | Triggered | Generic Database Assignment | 92a577bd4e7b64860b2fff7991e605c3903050f5 | Interface/ai_service.py | [View secret](https://github.com/COS301-SE-2024/Events-System/commit/92a577bd4e7b64860b2fff7991e605c3903050f5#diff-e8e40c2bfea79683d0cac5ed12f301c81e456f846009e3231ceed86326a25cbdR25) | | [13861047](https://dashboard.gitguardian.com/workspace/301252/incidents/13861047?occurrence=166141716) | Triggered | Generic High Entropy Secret | d3ffe979b458abf3d123e75f36c16ff87371ff13 | .npmrc | [View secret](https://github.com/COS301-SE-2024/Events-System/commit/d3ffe979b458abf3d123e75f36c16ff87371ff13#diff-e813096d69c49812e40e00be9ac8fa14d77f0ec1f97ab4c45cb096b3bedd35deL2) | | [13861048](https://dashboard.gitguardian.com/workspace/301252/incidents/13861048?occurrence=166141715) | Triggered | Generic Database Assignment | d3ffe979b458abf3d123e75f36c16ff87371ff13 | Interface/ai_service.py | [View secret](https://github.com/COS301-SE-2024/Events-System/commit/d3ffe979b458abf3d123e75f36c16ff87371ff13#diff-e8e40c2bfea79683d0cac5ed12f301c81e456f846009e3231ceed86326a25cbdL25) |

🛠 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 secrets safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate these secrets](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/generics/generic_high_entropy_secret#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.

---

^{🦉 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.}