Ref. Symptoms / observations / job analysis feature

Context: This step focuses on automating the process of applying symptom labels to job runs when they are finished running. This part extends previous work to apply labels within the job intake cloud function (LoadJobRunData).

When finished.json is created (at the top of the prow job artifacts), apply compound symptoms based on the other labels applied.

• Define golang CEL inputs based on existing label IDs.
• For each compound symptom, evaluate the EL and add labels if indicated.
• Repeat until no further labels are added.

As much as possible, logic for determining labels and writing them should be located in the sippy codebase (and imported by the cloud function), to facilitate reuse by other tools doing the same things in different contexts.