fix(jobs): Limit command jobs to known cases

[nickvergessen]

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)

[nickvergessen]

/backport c0be533 to stable32

[nickvergessen]

/backport c0be533 to stable31

[nickvergessen]

/backport c0be533 to stable30

[nickvergessen]

/backport c0be533 to stable29

[nickvergessen]

/backport c0be533 to stable28

[skjnldsv]

What's the right new approach to add a command in our apps then @nickvergessen ?
Ah, ok Symfony\Component\Console\Command\Command directly. Let me write some docs

server/lib/public/Command/ICommand.php

Line 13 in 54efa19

* @deprecated 33.0.0 The interface is considered internal going forward and should not be implemented by apps anymore

[nickvergessen]

No, the coding pattern is discouraged and should not be used. If you need a command to be executed make it a command with explicit setup instructions of your app.
Clonking background jobs is not the intended way

[skjnldsv]

But was ICommand only reduced to background jobs?
Could I not register normal stuff like listing users with it ? (Random example)

Registering synchronous commands are still a proper acceptable pattern, right?

[skjnldsv]

nextcloud/documentation#14853 @nickvergessen