feat: Round Robin Skip If contact owner first available slot is more than 2 weeks, round robin as normal

[joeauyeung]

What does this PR do?

In a sales environment, we want prospects to book a time that is not too far out. If the contact owner does not have an open slot within two weeks, default to normal round robin (includes attribute routing)

• Fixes #XXXX (GitHub issue number)
• Fixes CAL-XXXX (Linear issue number - should be visible at the bottom of the GitHub issue description)

https://www.loom.com/share/251967b87fab4b028f3af7637ce3d270?from_recorder=1&focus_title=1

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

• Set the contact owner to be OOO for more than two weeks
• Route to the contact owner
• The routing should not be for the contact owner but for the other members

Checklist

• I haven't read the contributing guide
• My code doesn't follow the style guidelines of this project
• I haven't commented my code, particularly in hard-to-understand areas
• I haven't checked if my changes generate no new warnings

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "RR Skip: If contact owner first available slot is more than 2 weeks, round robin as normal". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[graphite-app]

Graphite Automations

"Add consumer team as reviewer" took an action on this PR • (10/31/24)

1 reviewer was added to this PR based on Keith Williams's automation.

[joeauyeung]

We move all this logic into a separate function. Since we need to calculate the availability of the contact owner. If the first slot is more than 2 weeks away we then need to calculate the availability of the other members.

[emrysal]

Can we be more specific in the typing here? just specify minimumBookingNotice as part of the event type.