regression: improves CalendarEvent status change schedule

[ricardogarim]

Proposed changes (including videos or screenshots)

This PR ensures that, on application startup, all busy events are correctly scheduled or removed. In a multi-instance setup, the scheduling logic must run on every instance to keep event schedules consistent across the cluster. No explicit locking is required, as the cronJobs package handles concurrency internally.

The schedule function is now triggered in the following scenarios:

• Creation or import of a new busy event
• Update to an existing event (time or busy status)
• Deletion of a busy event
• Completion of a status change job
• End of an event (to restore the original status)
• Outlook Calendar integration activation (ee/server/configuration/outlookCalendar.ts)

The scheduling process includes:

• Part 1: Schedule all events starting within the next minute
• Part 2: Ensure in-progress events have scheduled end times (e.g., for server restarts, imported events already in progress, or missed schedules)
• Part 3: Schedule the next check

Issue(s)

• CORE-1039
• feat: set busy status on calendar appointments #35474

Steps to test or reproduce

Further comments

[dionisio-bot]

Looks like this PR is ready to merge! 🎉
If you have any trouble, please check the PR guidelines

[changeset-bot]

⚠️ No Changeset found

Latest commit: 75bf05f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

PR Preview Action v1.6.0
🚀 View preview at https://RocketChat.github.io/Rocket.Chat/pr-preview/pr-35607/
Built to branch gh-pages at 2025-03-31 17:05 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[codecov]

Codecov Report

Attention: Patch coverage is 35.82090% with 43 lines in your changes missing coverage. Please review.

Project coverage is 59.66%. Comparing base (68dbd82) to head (75bf05f).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #35607      +/-   ##
===========================================
- Coverage    59.72%   59.66%   -0.06%     
===========================================
  Files         2829     2829              
  Lines        68230    68287      +57     
  Branches     15124    15141      +17     
===========================================
- Hits         40748    40742       -6     
- Misses       24874    24934      +60     
- Partials      2608     2611       +3     

Flag	Coverage Δ
unit	75.69% <35.82%> (-0.24%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ggazzo]

considering the number of lines, methods and the nature of the pr, I would say this is not a regression. s

[ggazzo]

I need to check what is happening here, its clearly more than a simple correction. putting my change request here just to prevent the ci to merge

[pierre-lehnen-rc]

still missing i18n key for the new setting

it looks like this time we're going to do an exception