Improve user listing performance for large installations

[kulmann]

Is your feature request related to a problem? Please describe.

User listings in the admin settings app can be quite expensive for large instances (especially because we expand certain fields in the listing already). We want to make it configurable if the user listing should happen upon first page load.

Describe the solution you'd like

• introduce a config option (web + ocis) for enabling or disabling the initial user listing request in the Users view of the admin settings. By default we want the initial user listing to happen.
• if initial user listing is disabled, the UI needs to make clear that results will only show if after a filter gets applied.
• Search field is currently client side filtering. We need to make use of the new contains backend side filter for the display name, see add user filter startsWith and contains ocis#7739
  • typeahead filtering on the username is too expensive. We want to apply the filter only after the user submits the input (= ENTER or submit button).
  • search term highlighting in the table should only highlight string parts in the display name column Admin settings fix mark problems, remove memberOf from list users query #10090
  • while at it, fix the wrong highlighting in the spaces view as well (should only highlight space name, not e.g. managers)
    Admin settings fix mark problems, remove memberOf from list users query #10090
• We found out that we don't need to fetch group membership while listing users Admin settings fix mark problems, remove memberOf from list users query #10090

Describe alternatives you've considered

• Server side pagination. Too expensive to build and especially not fully supported via LDAP.