Validate that having some filter presets that can be shared across the query team (or other teams) could improve error surfacing and root-case analysis.

Parsley already supports filter presets, but they are not widely used with at most 1 or 2 filters defined per evergreen project.

• filter presets can only be added by someone with necessary rights / privileges
• there is no name or comment annotating what the preset does (see DEVPROD-943)
• filters are per evergreen project (e.g., mongodb-mongo-master), and not per team or per individual (engineers store useful regular expressions in notes or Wiki pages)

If Parsley is to add support for filter presets per team, we need to make sure we have some of those and they are useful.

Since Parsley still does not support 'jq' filters, to profit from structured log we should perform validation in the command line using 'grep' and / or 'jq'. We can construct filters and apply them to already closed AF/BF/HELP issue logs to see if the filter helps to reveal the issue or the root cause.

We may need to involve other query team colleagues to collect useful filter presets and feedback in general.