Feature/implement company access level

What type of PR is this?

[x] ♻️ Refactor
[x] ✨ Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update

Description

This Pull Request aims to enhance the application by introducing validation checks for users associated with companies. The primary focus has been on ensuring that users can only perform actions within the context of their respective companies. The changes have been implemented in key endpoints, including the Login, User Creation, and User List methods.

Changes Made:

Login Endpoint: Added a validation step during user login to ensure that the provided company context is valid & Updated the authentication flow to consider the company context for authorization.
User Creation Endpoint: Extended the user creation process to include company association & Implemented a check to ensure that the specified company is valid before allowing user creation.
User List Endpoint: Modified the user list retrieval to filter users based on their associated companies & Introduced a company context parameter to restrict user list retrieval to a specific company.

Benefits

Improved security and data integrity by ensuring that users can only operate within the scope of their associated companies.
Enhanced user experience by providing accurate and filtered data for specific companies.

How I Tested This

Thoroughly tested the changes by creating and associating users with various companies.
Conducted positive and negative testing scenarios for login, user creation, and user list endpoints.
Verified that only authorized users can access and manipulate data within their respective companies.

Recordings

WhaTicket

Next Steps

As we are doing company creations through seed commands, it would be required to create a new screen/component to register new records of companies
Create more unit tests scenarios
Fix small issue of company selection at login screen, that it gets blank after filling email/pwd fields
Allow admin to view any company's contacts