[FEAT] Multitenancy: Add AuthorizedTenants to Workflow Definitions

We propose adding a list of `AuthorizedTenants` to workflow definitions. This feature will allow tenants to start a workflow they do not own. They will be able to view the workflow in read-only mode and initiate it, but they will not have the ability to modify it since they are not the owner tenant.

### Potential Extensions

If implemented, we could further enhance the authorization model by adding more detailed permissions to workflow definitions. For instance, this could enable:

- Allowing tenants to contribute to the editing of a workflow owned by another tenant.
- Defining specific roles and permissions for different tenants, thereby creating a more flexible and robust authorization system.

### Benefits

- Increased flexibility in workflow management.
- Enhanced collaboration across different tenants.
- More granular control over workflow permissions.

### Use Cases

- Tenants needing to start workflows that are not in their ownership.
- Collaborative environments where multiple tenants contribute to workflow development.
- Scenarios requiring detailed access control over workflow definitions.