Filtering should be case insensitive

In NEXUS-8844, I noticed that search had case sensitive filtering.
Kelly Robinson requested I make a generic ticket so solving that could be tackled globally.
This sounded familiar but I only saw a few tickets regarding individual areas and most of them NX2.
This is a blanket ticket/review of NX3.
I waffled between bug and improvement (maybe could also be technical debt or story) but based on the tickets I saw, it seems places were in NX2 and if not there were bugs so made a bug for now.
I didn't actually check all areas or older NX3 (or NX2) at this time.

As a user if I am looking for "U", I prefer not to filter twice.

Acceptance criteria (from me, maybe to be refined):

• Anywhere there is a filter and there cannot be a multiple case state (you cannot have "Joe" and "joe") that filtering should be case insensitive.
• The intent isn’t for the solution to be a huge monolithic effort. The output of the spike should be a series of smaller stories that let us implement the solution in a phased way.
• Timebox the investigative effort to half a day (should be enough to let us capture the most visible issues)