feat(userList): Allow to list all users

[solracsf]

• Resolves: Use --limit 0 to disable user:list limit  #57120

Summary

Updated the limit option to allow --limit=0 for unlimited users listing.

This PR simply passes null to underlying methods since IUserManager::searchDisplayName() and IUserManager::getDisabledUsers() accept null for the limit parameter.

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)

[kesselb]

🐘

[miaulalala]

What's the highest amount of users you've tested this with? I'm a bit worried about running out of memory - I think it would be wise to chunk the output to something like 500 or 1000 users per call to writeArrayInOutputFormat

[come-nc]

@miaulalala You would still have all users in memory, no?
The issue is that the offset in userManager cannot really be used, because depending on the backend it’s really bad (for LDAP for instance).

[solracsf]

What's the highest amount of users you've tested this with?

11.768 in a public instance (using LDAP).

cleared

[solracsf]

Also please note that this PR is not different from something like occ user:list --limit=99999999 so the user can already list all users. This PR just simplifies and documents the process :)

[szaimen]

/backport to stable33

[szaimen]

/backport to stable32

[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/57179/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 b5852805

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/57179/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.

[szaimen]

/backport to stable33

[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/57179/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 b5852805

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/57179/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.

[szaimen]

Apparently this was merged before the 34 branch-off already. So no backport to stable33 required