feat: add ability to filter jobs by tags

[golanglemonade]

We have a lot of jobs with the same kind, but different tags. This will make it much easier to filter the data and find jobs.

[brandur]

@codex review

[chatgpt-codex-connector]

Codex Review: Something went wrong. Try again later by commenting “@codex review”.

An unknown error occurred

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[brandur]

Thanks @golanglemonade! Thoughts on autocomplete for tag names? A bit harder maybe than queue names or job kinds, but seems like it'd be make the feature a lot more useful.

[brandur]

Think this whitespace is wrong and should go back to how it was before.

[golanglemonade]

Thanks @golanglemonade! Thoughts on autocomplete for tag names? A bit harder maybe than queue names or job kinds, but seems like it'd be make the feature a lot more useful.

Yep, I actually had a working automcomplete, but required direct sql because the riverdrver doesn't support the query, but I figured the preferred path would be to query the riverdriver with the update and then come back and add auto complete here?

rows, err := pgxTx.Query(ctx,
    `SELECT DISTINCT tag
    FROM river_job, unnest(tags) AS tag
    WHERE ($1 = '' OR tag ILIKE '%' || $1 || '%')
		    AND ($2 = '' OR tag > $2)
		    AND ($3::text[] IS NULL OR tag != ALL($3))
    ORDER BY tag ASC
    LIMIT 100`,
    match, after, excludeArg,
    )

[brandur]

Ah nice. Yeah, there won't be a drive function for that.

@bgentry We better get your input before @golanglemonade goes too much further with this one. Is there a reason this feature didn't exist in the beginning, or just was never implemented?