Add team deck integration with routing and component support

[hefftich]

• Resolves:
  Display the team Deck boards within the Teams app #2948

• Requires:
  Add embeddable board web-component deck#8543

Summary

Embed Deck boards directly within Teams without an iframe or switching
to the standalone Deck app, preserving the active team context.

• Keep the team navigation visible and highlight the active board,
  including when viewing card details.
• Add team-scoped board and card routes with deep-link and browser
  back/forward support.
• Preserve the embedded board instance across card navigation and
  dispose it when switching boards, teams, or resource views.
• Open personally shared boards within Teams and validate navigation
  against the current team's resources.
• Add backend and frontend regression tests.

The integration requires a Deck version providing the
nextcloud-deck-board web component and LoadBoardWebComponentEvent.
Older or disabled Deck installations show an explicit unavailable state.

TODO

• ...

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 ( GPT-6.1 Sol)

[codecov]

Codecov Report

❌ Patch coverage is 88.04348% with 11 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/teams/views/TeamDeckView.vue	85.33%	5 Missing and 6 partials ⚠️

📢 Thoughts on this report? Let us know!

[artonge]

As an overall comment, the solution needs to be application agnostic as we will want more than deck board in the future, and we cannot have a custom handling for each new ressources that we want to dispay.

This means that we need to create a propre API for such thing, where apps can register ressources to be displayed. Then circles would simply consume this API to display an arbitrary number of ressources without needing to know about them. This would be really close to the smart picker widget API, so maybe we can extend it, or inspire ourselves from it for the new API.