feat: Add name filters for workflow list (exact/prefix/pattern)

[Adrien-D]

Fixes #12161 1/2 (I'll make a PR for filtering archived/non-archived workflows on a seperate PR)

Motivation

We used to have name/prefix filtering for archived workflows before unifying APIs. We need to implement it back.

Modifications

API :

• Name filtering was already implemented
• I plugged back the NamePrefix to make it work
• I added NamePattern the same way prefix is implemented

UI :

• As its three way of filtering, and no reason to have those three at the same time, I made UX choice with a picker on the label. This is inspired from grafana's UI.

Verification

I tested the feature locally and I added tests for the API.

[agilgur5]

Left several suggestions, simplifications, style fixes, etc in-line below.

Might have a few more after that, particularly on the UI component and CSS changes that I did not check closely on this pass

[Adrien-D]

I fixed my PR with your suggestions. Please note that I updated argo-ui package to last merged commit to be able to remove autoHighlight (one of my other fixed issue) on this particular autocomplete component

[agilgur5]

Please note that I updated argo-ui package to last merged commit to be able to remove autoHighlight (one of my other fixed issue) on this particular autocomplete component

Mmm I wouldn't include that as part of this PR since it is independent. Like we'd probably want to cherry-pick the argo-ui update/fixes into 3.4, which this PR will ofc not make it into.

Also there isn't an autocomplete component used in this PR?

[Adrien-D]

Also there isn't an autocomplete component used in this PR?

There is, it's the component behind InputFilter used for filtering

But I get your point, we can merge this PR without it and I'll make two other PR to update the argo-ui package, and fix the behavior here

[agilgur5]

A few more comments on the filters below.

I haven't had time to take a look at the "contains" wording or CSS since I'm on vacation for the rest of the week and not at my computer

[agilgur5]

I'm wondering if we should make the API match the UI actually; name as a string and nameFilter as an enum that defaults to "Exact"

Right now, it's not clear that these are mutually exclusive. We could add that in the comments, but having it only allow one at a time feels much more explicit

[Adrien-D]

Yeah I like that idea, so we could have nameFilter as Exact | Contains | Prefix, and then nameValue as string

I'm not familiar with the use case, but does it make more sense to have Exact as default instead of Contains ?

[agilgur5]

Exact as default would be backward compatible, since previously it was the only usage of name.

We don't have to keep that default in the UI, but it would be necessary in the API for backward compat