Run tag queries removed from dequeue process

The run engine's dequeue process is shedding some unnecessary weight. Previously, the system fetched all associated run tags every time it dequeued a run for processing. Now, the engine skips this step entirely.

By dropping the tag query from the dequeue payload, the system pulls less data from the database on every cycle. This streamlined approach should translate to faster queue processing and reduced database strain, especially during high-volume traffic spikes. The change makes the core dequeue loop leaner and less prone to performance bottlenecks.