feat: org-wide workflows

[CarinaWolli]

What does this PR do?

• Org-workflow can be set active on teams and will trigger for all the team event types + all the user event types of the team members.
  • if a user is member of several active teams, the workflow only triggers once
• Add 'apply to all, including future teams/event-types'
• workflows/update.handler is refactored into smaller functions that can be reused and tested.
• Also fixes some small existing bugs that I found when refactoring the code

Todo:

• When member is removed from team and workflow has 'active on all, including future' set then reminders aren't deleted (reminders should be deleted if user isn't member of any other team)
• should org workflow be triggered if user is not part of any team?
• write unit test for deleteWorkfowRemindersOfRemovedMember

Follow ups:

• Create Workflow repository to handle data operations
• Improve types, for example: https://github.com/calcom/cal.com/pull/15083/files#diff-40b6e69d629325f5d2e47bb383fce1847ed9f69f763d0b92ae8067477fad2d24R30
• feat: org-wide workflows #15083 (comment)

Fixes #14638
Fixes CAL-3489

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected)
• I have added a Docs issue here if this PR makes changes that would require a documentation change --> Created an issue for that: Org-wide workflows docs#93
• I have added or modified automated tests that prove my fix is effective or that my feature works (PRs might be rejected if logical changes are not properly tested)

How should this be tested?

Basic test:

• Create an org workflow
• Set active on a team (or all teams)
• Book a team event type --> see if workflow triggers
• Book a user event type of a team member --> see if workflow triggers

Test other cases, for example:

• test with several teams when some team members are part of several teams --> a workflow should always just trigger once
• Test updating a 'before event' workflow and see if WorkflowReminders are correctly adjusted
• Test removing team workflow and see if reminders are deleted (if user is still part of another team that is active, the reminder should stay)
• delete/add reminders for deleted/added steps
• Add reminders for new active teams
• Test if 'active on all teams/even-types, including future ones' works with new event types/teams

[hariombalhara]

Amazing work @CarinaWolli 🎉 It is a complex addition to workflows affecting a lot of places.

It was great reviewing this with your speed of iteration as well !!

I am not sure if we should merge this now or wait till after the retreat as it is a big PR.

[hariombalhara]

Amazing work @CarinaWolli 🎉 It is a complex addition to workflows affecting a lot of places.

It was great reviewing this with your speed of iteration as well !!

I am not sure if we should merge this now or wait till after the retreat as it is a big PR.

Also, someone else who has more experience with workflows should also review this to ensure the entire functionality is working

[Udit-takkar]

@CarinaWolli can i disable global org workflow on any event type?

I see the message "Locked by team admin" even on my personal event types

[CarinaWolli]

@CarinaWolli can i disable global org workflow on any event type?

I see the message "Locked by team admin" even on my personal event types

org workflows can't be disabled on any event type, that's by design

[Udit-takkar]

LGTM. Great work.

tested org, team and user workflows.
The only thing we can improve is to divide the large functions ( like scheduleBookingReminders) into smaller, more manageable functions.

[keithwillcode]

@emrysal @zomars Just spoke with @CarinaWolli and we are going to wait until post-retreat to merge this. Moving back to draft for that reason.