Comment 1 for bug 1910424

Noting an implementation detail: for small tables, SQL queries that use ILIKE or case-insensitive regular expressions aren't a big deal. However, a case-insensitive substring search on a column that isn't indexed appropriately could be very slow, so some attention should be paid to that consideration.

This is probably not a practical problem for all or almost all of the tables in the config schema, but it very much could be a huge deal for certain other grid filters.

Consequently, I propose the following:

- add a Boolean grid-level setting for case-insensitive text filters, defaulting to false
- add a column-level setting that can override the table-level setting
- have the setting adjust the labels on the filter operators to hopefully reduce the chance for user confusion (or have the setting add case-insensitive versions of the operators, but that might be overkill)
- turn the grid-level setting on for all (or almost all) Angular grids drawing from configuration tables, including making it default to true for the auto-generated interfaces
- think _carefully_ about turning it on elsewhere without first verifying that appropriate indexes are in place