feat: add occ command to scan and delete orphaned keys

[hamza221]

Summary

As an administrator I want to be able to delete encryption Keys that are orphaned ( the encrypted file was deleted without the corresponding key)
encryption:clean-orphaned-keys scans all users' filesytems for default module encryption Keys and lists them with possibility to delete all of them or specific ones

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)

[come-nc]

It would be better to use Node API intead of View.
Also it feels you took inspiration from EncryptAll which since got cleaned up: #55472

[hamza221]

/backport to stable30

[hamza221]

/backport to stable31

[hamza221]

/backport! to stable30

[hamza221]

/backport to stable32

[come-nc]

I think it would be better to allow either printing/deleting on the go or limit to some users to avoid having to run on all the users in one go, which on some big instances will be an issue, but this can be improved in follow-ups, we should merge this as a first version.

[backportbot]

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

# Switch to the target branch and update it
git checkout stable30
git pull origin stable30
# Create the new backport branch
git checkout -b backport/55556/stable30
# Cherry pick the change from the commit sha1 of the change against the default branch# This might cause conflicts, resolve them
git cherry-pick f1cdf688
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/55556/stable30

Error: Failed to create pull request: Validation Failed: {"resource":"PullRequest","code":"custom","message":"A pull request already exists for nextcloud:backport/55556/stable30."} - https://docs.github.com/rest/pulls/pulls#create-a-pull-request

---

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

[hamza221]

I think it would be better to allow either printing/deleting on the go or limit to some users to avoid having to run on all the users in one go, which on some big instances will be an issue, but this can be improved in follow-ups, we should merge this as a first version.

tracked here #56349