Add checks to "Label Added" triggers

[erictncabramson]

User Story As a user, I want my labels to be limited to those actually available, so that my rules and triggers actually work

Acceptance Criteria A few different options. Perhaps there is an "MVP" --> "Ideal" approach

• Option 1:
  • When using "Label added" as a trigger, replace the text input with a dynamic drop down of labels predicted by ML models invoked in prior automation rules.
• Option 2:
  • Keep the text input, but validate against the labels predicted by other ML models in prior automation rules and display a warning message (copy to come later) that the label they've entered isn't predicted by any currently configured model.

Notes:

• We may want to also run these checks in the AutomationRulesList.jsx component too, in case a user deletes an Automation Rule that breaks the pipeline.
• How do we ensure that any user-created labels are also available for their choice? Aka not accidentally limit them to just model predicted labels? Or if we are stuck doing that right now, how do we make that super clear?
  • From @lessej: "Another minor clarification that would be helpful is "label added" only applies to labels added by ML models. It's pretty obvious after you start using Animl but in a project with megadetector -> speciesnet, the first few times I added a label I was unsure if manually adding "animal" would kick off speciesnet"