We'll need to amend this to take into account matching tags. Queue position could be 1/3 for the provisioners that match, but 20/50 on a larger scale (but that's nonsensical). Do we have an issue that tracks this?

Originally posted by @mafredri in #15835 (comment)

GetProvisionerJobsByIDsWithQueuePosition currently calculates queue position regardless of tag set. We should calculate queue position separately for each tag set in this query.

Note: this gets slightly more complex when we also take into account that tag sets are equivalent regardless of ordering (e.g. {"foo":"1", "bar":"2"} is equivalent to {"bar":"2", "foo":"1"}.