feat: Add back searching in disabled user list

[come-nc]

• Resolves: [Bug]: Search in the"disabled users" section does not work #44936

Summary

When disabled users where moved to their own endpoint we overlooked search, so adding it back.
The search is done case-insensitive in uid and display name.

TODO

• Decide if we should also search in email field, and implement it
• Decide if the BC break is ok or should be avoided with a new interface

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)

[come-nc]

TODO

• Decide if we should also search in email field, and implement it

Implemented.

• Decide if the BC break is ok or should be avoided with a new interface

I think this is fine, because a class implementing the interface for 30 also implements the one for 28.0.0, as it’s only a new parameter.
So, as the breaking is minimal and it’s easy for concerned apps (and that’s only apps implementing a user backend with special disabled user treatment, so only user_ldap to my knowlegde) to support all Nextcloud versions.

[come-nc]

/compile /

[provokateurin]

I would prefer separate methods for searching quite a lot over changing the behavior of the existing methods. Would that be possible or is it too much work or impractical?

[provokateurin]

Ok in light of the discussion in #44936 it makes sense to extend the existing endpoint instead of creating a new one

[artonge]

So BC is not a real BC?

Edit: seen your second comment

[come-nc]

/compile /

[come-nc]

/backport to stable29

[come-nc]

/backport to stable28

[nickvergessen]

@come-nc Please document in https://docs.nextcloud.com/server/latest/developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_30.html#id2