[Enhance] Employee-Organization Association and Activation Flow

[samuelmbabhazi]

Problem:

• A user registered as an employee in an organization can create or be associated with other organizations within the same tenant. However, the current system limits employees to be active or inactive in a single organization, making the organization selector redundant when multiple organizations exist.
• Deactivating an employee for an organization currently impacts the user's ability to manage multiple organizations
• If an employee is marked Inactive for the first organization, the user can't be set as Inactive because they may still have access to another organization.
• Inactivating a user would prevent them from logging into any organization, including the ones where they are still active.

Proposed Solution:

Organization-Based Inactivation: Instead of inactivating the user globally, allow inactivation of the employee's association with a specific organization. This way, the user can still access other organizations where they are active.

Multiple Organization Management:

• An employee should have the ability to track time and manage tasks across multiple organizations .
• This will ensure that the organization selector (already available in the Desktop App and Gauzy UI) has meaning and purpose, allowing employees to choose which organization they want to work on.

Additional Details:

• Users can be associated with many organizations, so the organization selector should let users switch between active organizations.
• Employees and their relations to organizations should be independent, meaning an employee can be active in one organization but inactive in another.