Improve consistency of `FilterEdit` behavior

[negasora]

Various FilterEdits have very different behavior.

A non-exhaustive list includes:

• Using the input as a case insensitive substring search
• Using the input as a case sensitive regex
• Using the input as a case insensitive regex
• Using the input as a space-separated list of case-insensitive substrings to search for
• Using the input as a space-separated list of case-insensitive regex substrings to search for

We should have FilterEdit use a simple, case-insensitive substring search by default and, if we want that instance to support regex, have an optional toggle a la vscode and many other interfaces.

We should also consider adding a case-sensitivity toggle as well.

[WeiN76LQh]

I find particularly with searching symbols it can be quite confusing about the matching algorithm. Sometimes its way to permissive about how it works and IIRC things like a bracket ( are considered regex and won't match literally

[negasora]

Regex and case-sensitivity toggles added to some inputs in 5.3.9080-dev, other FilterEdits' behaviors are much more consistent now