fix(files_trashbin): misleading trashbin:expire output when expiration is disabled

[joshtrichards]

When trashbin_retention_obligation is set to disabled, trashbin:expire incorrectly reports the auto-expiration policy and exits with a failure status.

Report that automatic expiration is disabled and exit successfully instead.

• Resolves: #n/a

Summary

Discovered while working on nextcloud/documentation#15421

Fixes the output and exit status of occ trashbin:expire when automatic trash-bin expiration is disabled with:

'trashbin_retention_obligation' => 'disabled',

When expiration is disabled, trashbin:expire currently prints a message describing the default auto policy:

Auto expiration is configured - keeps files and folders in the trash bin for 30 days ...

It also exits with status 1, even though the configured state is valid and no operation has failed.

This is misleading.

Changes:

• Report that trash-bin expiration is disabled.
• Clarify that no files or folders will be automatically expired by the command.
• Return exit status 0 for this valid no-op condition.

Only updates occ trashbin:expire output/return value behavior for the disabled retention policy. It does not change retention-policy semantics or the behavior of trashbin:cleanup or any other aspect of the implementation.

TODO

• n/a

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)

AI (if applicable)

• The content of this PR was partly or fully generated using AI