feat: automatically create a teamfolder upon team creation

[stediefan]

feat: introduce a function to upgrade existing teams to include the special teamfolder
feat: add settings page to configure a default quota for new teamfolders

Assisted by: GitHub Copilot:Claude Sonnet 5
Assisted by: GitHub Copilot:GPT-5.6 Terra
Assisted by: GitHub Copilot:Kimi K2.7 Code

• Resolves: Create team-folder when creating a team #2661, Show team-folder contents on the TeamPage #2663, Upgrade existing teams: create a path to turn a pre-existing team into a space (team+team-folder) through the same dialog and quota rules, reusing resources it already has instead of creating duplicates #2669

Summary

This is a aggregated feature that integrates teams with teamfolders. The teams feature aims to provide a space for team owned apps. This provides the base as the linked groupfolder is the proposed solution.

TODO

• Related Pull Request in server: feat: introduce a function to bind a teamfolder to a team server#62476
• Related PR in Groupfolders: feat: add event handling to auto create teamfolders upon circle creation groupfolders#4941
• Documentation should propably be more broadly?

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
  The newly introduced feature to set a default Quota for the auto created folders:

The view for teams with a linked folder:

• Documentation (manuals or wiki) has been updated or is not required
  see todo
• Backports requested where applicable (ex: critical bugfixes)
  no
• 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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[cristianscheid]

overall the pr looks good to me (focused more on reviewing the backend part, which is the part I'm more familiar with)

left two comments (non-blocking in my opinion)

[cristianscheid]

@stediefan npm lint errors are related to this PR's changes, could you please fix them? should be able to do so by running npm run lint from inside circles app folder

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)