Feat: Restrict Event Booking to Verified Users

[samar12-rad]

Describe the feature

Description: Currently, the event booking page allows all users to access the "Book Now" feature. To enhance security and improve the user experience, only logged-in or verified users should be able to book new events. Non-authenticated users should be redirected to the login page if they attempt to book an event.

Acceptance Criteria:
Users who are not logged in should not be able to access the event booking functionality.
If a non-logged-in user clicks "Book Now," they should be redirected to the login page with a message prompting them to log in.
Logged-in users who have verified their email (or passed other verification criteria) can book new events.
Backend should verify the user's authentication and verification status before processing the booking request.

Tasks:
Implement authentication check in the frontend to disable "Book Now" for non-authenticated users.
Add redirect to login page when a non-logged-in user tries to book an event.
Modify the backend API for booking events to validate that the user is authenticated and verified.
Test with different user scenarios (logged-in, logged-out, verified, unverified).

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I have starred the repository
• I'm a gssoc-24-extd contributor
• I want to work on this issue

[github-actions]

Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions or additional information, feel free to add them here. Your contributions are highly appreciated! 😊

You can also check our CONTRIBUTING.md for guidelines on contributing to this project.
for more information join our discord https://discord.gg/Jh3bWQ7FRN

[RamakrushnaBiswal]

@samar12-rad assigned

[haseebzaki-07]

hey @RamakrushnaBiswal can I work on this issue??

[RamakrushnaBiswal]

Sure @haseebzaki-07

[github-actions]

Hello @samar12-rad! Your issue #298 has been closed. Thank you for your contribution!🚀