Added the feedback form(both frontend and backend logic)

[Praveenkumar5048]

Related Issue

This pull request is related to issue #234

Description

1. The have Completed the implementation of feedback form.
2. "Give Feedback" button in the footer section, clicking on this, feedback modal opens up, user gives their details and write feedback and also rate our app experiance on a scale of 5.
3. This information is stored in the mongoDb
4. I have added mongodb model for feedback, and also created route and controllers folders for handling http request from frontend.

Type of PR

• [ ] Bug fix
• [X ] Feature enhancement
• [ ] Documentation update
• [ ] Other (specify): ___

Screenshots / videos (if applicable)

Checklist:

• [ X] I have performed a self-review of my code
• [X ] I have read and followed the Contribution Guidelines.
• [X ] I have tested the changes thoroughly before submitting this pull request.
• [ X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
• [X ] I have commented my code, particularly in hard-to-understand areas.

Additional context:

I request the admin to please review my code and merge this PR. I am open to any suggestions or modifications Thank you

[vercel[bot]]

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

Name	Status	Preview	Comments	Updated (UTC)
kaam-do	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 24, 2024 5:44pm

[github-actions[bot]]

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

[PatilHarshh]

conflicts

[Praveenkumar5048]

@PatilHarshh I will recheck my code and try to resolve the conflicts

[Praveenkumar5048]

@PatilHarshh i have resolved the conflicts and incorporated latest changes into my code from the main branch. I have created a new PR resolving these issues, please go through that and merge my PR.

Thank you

[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 | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [11775317](https://dashboard.gitguardian.com/workspace/557539/incidents/11775317) | Triggered | Generic High Entropy Secret | 6aaa592a42f421dedb662b45d304e1dd900db17d | client/dist/assets/index-1f76e8ca.js | [View secret](https://github.com/PatilHarshh/Kaam-Do/commit/6aaa592a42f421dedb662b45d304e1dd900db17d#diff-9b549d38729ade3223a624c409cd3f5dcf6cd685d44ef5e3709dd73689aed465R21) |

🛠 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](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 this secret](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.}

[Praveenkumar5048]

@PatilHarshh please review my code, it doesn't contains any merge conflicts, merge this PR