Feat(REST API): add url to (un)archive cards

[xyjonas]

• Resolves: (Un)Archive cards programmatically via REST API #6132
• Target version: main

Summary

I implemented two new routes /api/v{apiVersion}/boards/{boardId}/stacks/{stackId}/cards/{cardId}/archive & /api/v{apiVersion}/boards/{boardId}/stacks/{stackId}/cards/{cardId}/unarchive, that will archive/unarchive cards via cardService. Documentation and unit tests are also included.
Please review my work and let me know what you think.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Documentation (manuals or wiki) has been updated or is not required

[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.)

[juliushaertl]

Thanks for your pull request and sorry for taking so long to review. Generally this seems good to me. However since this is a new endpoint we need to bump the API version so that clients can detect if the new API endpoint is actually available in https://github.com/nextcloud/deck/blob/fix/nextcloud-30-design-issues/lib/Capabilities.php#L39