User list export: apply filters (fixes #298)

[Trigary]

Summary of changes:

• The implementation behind the export button on the /users route has been replaced
  • The rendering has been moved from list.blade.php to list_users_component.blade.php
  • Clicking the button no longer calls the users.export route: the click is now handled within the livewire component
  • The same filtering logic is used within the component for the display of the users and for the exporting
• To implement the filtering, a UserFilter utility class has been created
• The different Export classes under UsersSheets have been modified so that the included users can be specified
• The behavior of the users.export path (hopefully) hasn't changed: the same users will get included in the exports as before

Small, mostly unrelated fixes:

• The $show_feedback property has been deleted from SemesterEvaluationExport: it was unused
  • UsersExport also assumed that SemesterEvaluationExport had a boolean constructor parameter, while in fact, it did not have any parameters. This has also been fixed.
• ListUsers's status related methods incorrectly named their parameters status_id, while in reality they received a status (string), not an ID

[Trigary]

The new scopeWithAllRoles doesn't (yet) support specifying role objects and the new tests don't use role objects. Let me know if I should change that.

[kdmnk]

The new scopeWithAllRoles doesn't (yet) support specifying role objects and the new tests don't use role objects. Let me know if I should change that.

Yeah I was also thinking about that but honestly I kind of want to rewrite the whole scope to support multiple roles in an optimal way and then use the scope for the hasRole function.

Whether to support object arguments or IDs is also a debatable. Objects improve readability and static typing whereas IDs are usually more optimal (if you only have the id you should be able to pass it as it is).

In short, it's fine by me, but feel free to investigate it further.

I'll take a look at this whereHas use case later, seems strange.

[kdmnk]

FYI you can use https://laravel.com/docs/11.x/queries#debugging to see make sure the queries are good. Or also in laravel debugbar.

[kdmnk]

Checked the docs. LGTM, if you want to merge now.

[Trigary]

I want to merge now.