feat: add a search page for groups

[lorenzo-cavazzi]

Work in progress

/deploy renku=lorenzo/groups-search

[RenkuBot]

You can access the deployment of this PR at https://renku-ci-ui-3735.dev.renku.ch

[leafty]

@lorenzo-cavazzi I would expect that all search pages use the same logic in the future. Having the logic in a redux slice makes that very easy to re-use in the different search pages. If we don't do that now, then we should document it so that we refactor the code for search to always use the same logic and components.

For reference:

• Global search page -> should use the new search logic in the future
• Group search page -> nice new search
• User search page -> to be implemented

[leafty]

Code smell: this is used for something that does not require layout attributes. It means the hook logic is probably buggy or that the hook doesn't implement correct cleanup.

Use useEffect() and update the hook if necessary.

[lorenzo-cavazzi]

I agree that using useLayoutEffect isn't the cleanest way to address the problem. I couldn't make useEffect work as expected in some corner cases, but perhaps the cleanest approach here is to drop useEffect and use React Router navigation synchronously.

Here are the changes a2b4214

[lorenzo-cavazzi]

@leafty I fixed (hopefully) all the double-navigations cases and dropped useLayoutEffect. I added some notes about the components intended future

[leafty]

This breaks the onBlur feature (searching when onBlur happens). In this case, let's just remove this handler entirely because it is an anti-pattern to do what the code is doing here.

[lorenzo-cavazzi]

I like the fact that we search onBlur; if not, it would be best to reset the input when users click on filters to avoid confusion.
After reading more about why the onBlur behavior was overlapping with the submit, the trivial fix is to fall back to the form's submit explicitly instead of invoking the same function separately.
I changed that here c84b2e8

[leafty]

Otherwise should be OK to go.

[leafty]

weird behavior when switching entity types and the keywords are not shared:

Screen.Recording.2025-07-18.at.14.27.38.mov

[leafty]

LGTM

We can fix the issue above later if needed.

[lorenzo-cavazzi]

@leafty since I was at it, I fixed the highlighting issue in e2cc503
I also fixed a tiny problem when updating keywords in projects -- if you dropped a keyword, no "update" was possible (see b46d49c).

Could you re-approve?