[SebastianKrupinski]

Summary

• Resolves: # Client Ticket
• Added migration to allow setting subscription calendar transparency
• Added transparency interface for calendars to implement
• Modified all relevant files to include calendar subscriptions in free/busy

Testing

• Add calendar subscription with events that have a opaque transparency, open free/busy to see if the subscription events show time slots as busy

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI

[SebastianKrupinski]

/backport to stable35

[SebastianKrupinski]

/backport to stable34

[SebastianKrupinski]

/backport to stable33

[ChristophWurst]

PR is AI assisted but lacks the commit trailer

[ChristophWurst]

Document why this is added and how it can be tested. Right now I don't see how this is a fix that needs backporting.

[SebastianKrupinski]

Document why this is added and how it can be tested. Right now I don't see how this is a fix that needs backporting.

We discussed this, this morning. I've added testing instructions

[ChristophWurst]

Discussing in a call is not documentation. There are three other reviewers who have no chance of understanding the context of this change.

We discussed how subscriptions should be handled in free/busy and the decision was to make the transparency an option. This is pretty much a new feature. I do not see a strong reason why this needs to be backported.