Ref. Symptoms / observations / job analysis feature

Context: This follows on to TRT-2378 which (for an MVP) enhanced the JAQ (Job Artifact Query) dialog to allow users to save queries as symptom specifications.

These improvements were left for this Jira, although we could also decide to omit them: 

• Symptoms are loaded in two effects, once for the "common queries" list, once for the create/update section (to avoid duplicate names); combine these in one effect, to be re-triggered after a symptom is written.
• Populate the listed autocomplete options in the file match and the content match UI from existing symptoms with the same type of content match, instead of just a hardcoded list.
• When saving a symptom, validate that the file pattern and (for regex matchers) regex are compiled correctly by their corresponding libraries so that it can actually be applied in the cloud function.
• When labels are selected for a sympom, show the ID, title, and description (perhaps in a tooltip from the chip?)
• The Applicability Filter options are hardcoded (except the releases themselves) - should really come from the releases table, although they don't change often. This would require expanding the data returned in the releases API.
• Search for "rgba()" in the JAQ React component props, and use/define colors in our css file instead.