Fix automation tag filters to use AND logic instead of OR

[devin-ai-integration]

When multiple tags are selected in the automation trigger UI, the UI serializes them as a single match_related object with all tag IDs in an array:

{
  "match_related": {
    "prefect.resource.role": "tag",
    "prefect.resource.id": ["prefect.tag.X", "prefect.tag.alerting_on"]
  }
}

The backend evaluates this as OR (match any of these tags), but the UI presents tags as additive filters, implying AND logic. This is a UX gotcha reported by users.

Fix

buildMatchRelated() now produces separate match_related objects per tag:

{
  "match_related": [
    { "prefect.resource.role": "tag", "prefect.resource.id": "prefect.tag.X" },
    { "prefect.resource.role": "tag", "prefect.resource.id": "prefect.tag.alerting_on" }
  ]
}

The backend already evaluates an array of match_related objects as AND (all(match.includes(related) for match in match_related)).

Flow selection is unchanged — multiple flows still use a single object with an array of IDs (OR: match any of these flows), which is the correct semantic for "runs of flow A or flow B".

Files changed:

• automation-schema.ts — match_related type now accepts ResourceSpecification | ResourceSpecification[]
• flow-run-state-trigger-fields.tsx — buildMatchRelated() emits array for tags; extractors handle both formats
• use-edit-automation.ts — Preserves array match_related from API instead of collapsing to first element
• custom-trigger-fields.tsx — Handles array match_related type safely
• Tests and stories updated

Checklist

• This pull request references any related issue by including "closes <link to issue>"
  • This addresses a UX issue reported via internal Slack: automation tag filters producing OR instead of AND logic
• If this pull request adds new functionality, it includes unit tests that cover the changes
• If this pull request removes docs files, it includes redirect settings in mint.json.
• If this pull request adds functions or classes, it includes helpful docstrings.

Link to Devin session: https://app.devin.ai/sessions/4da47f4177f844f6b9d33d0953d69a35
Requested by: @zzstoatzz

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring