Auth: Implementation of org access control

[nishika26]

Summary

Target issue is #155 and #154
Explain the motivation for making this change. What existing problem does the pull request solve?
These issues were clubbed together because the final product of both of them is to put access control on authenticated user so that they can only create or access their organization only.

Notes

• Refactored Access and Creation Check Logic:

The check_org_access function has been introduced to streamline access control by handling both:

Access Control: Ensures that regular users can only access organizations they belong to. A 403 HTTP exception is raised if they attempt to access an unauthorized organization.

Organization Creation and deletion Permission: Only a superuser is allowed to do both of these

Note that a superuser still has access to everything.

• for Users Logged in via Username and Password:

If a user logs in using their username and password, the system will search the API key table using the user's ID to retrieve the associated organization ID. Access is only granted to the organization linked to their user ID in the API key table.

This approach is necessary because, at present, the API key table serves as the only link between users and organizations.

[codecov]

Codecov Report

Attention: Patch coverage is 93.33333% with 3 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
backend/app/api/routes/organization.py	75.00%	3 Missing ⚠️

📢 Thoughts on this report? Let us know!

[vijay-T4D]

Approved. - good for merge