Move invite-accepted capability and implementation to contacts app.

[redblom]

• Resolves: #

Summary

Code moved to contacts app, see nextcloud/contacts#4417

TODO

• deal with inviteAcceptedDialog code

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)

[ChristophWurst]

@redblom why is this moved out of server and could it break OCM when the contacts app is not installed? the app is not shipped. it is optional.

[ArtificialOwl]

@redblom why is this moved out of server and could it break OCM when the contacts app is not installed? the app is not shipped. it is optional.

This is done on my request:

• it is moved out of server because the implementation of the feature creates its own db table and does not provide an API to manage it,
• it will not break OCM, it will only not enable the 'invite-accepted' capability if contacts is not installed. the capability is useless without the contacts app,
• contacts will register the capability and fully manage the db table

[ArtificialOwl]

let's ping @mickenordin on this one !

[mickenordin]

let's ping @mickenordin on this one !

I haven't reviewed the change, but in principal I see no problem with it.

[redblom]

Rebased, squashed, removed draft label.

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

[redblom]

Rebased from master.

[miaulalala]

LGTM, all changes implemented

[miaulalala]

@ArtificialOwl your review would be apprechiated

[miaulalala]

@redblom can you sqash you commits please?

stale

[welcome]

Thanks for your first pull request and welcome to the community! Feel free to keep them coming! If you are looking for issues to tackle then have a look at this selection: https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22

[backportbot]

The backport to stable33 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable33
git pull origin stable33

# Create the new backport branch
git checkout -b backport/57853/stable33

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 5cbdfac0

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/57853/stable33

Error: Failed to check for changes with origin/stable33: No changes found in backport branch

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[miaulalala]

Congrats @redblom! Christoph left a comment on the contacts PR - that will need to be addressed, then we're done 🥳

[miaulalala]

/backport to stable34

[miaulalala]

/backport to stable33

[backportbot]

The backport to stable34 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable34
git pull origin stable34

# Create the new backport branch
git checkout -b backport/57853/stable34

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 5cbdfac0

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/57853/stable34

Error: Failed to check for changes with origin/stable34: No changes found in backport branch

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[backportbot]

The backport to stable33 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable33
git pull origin stable33

# Create the new backport branch
git checkout -b backport/57853/stable33

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 5cbdfac0

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/57853/stable33

Error: Failed to check for changes with origin/stable33: No changes found in backport branch

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.