Replace goroutine with unlimited buffered channel

[peterebden]

As discussed, I think we have potential ordering issues by dispatching things in separate goroutines. That was necessary to avoid blocking when sending to a channel if the receiver is slow.

This removes the goroutine and replaces it with a self-buffering channel-like thing which should maintain send order.

Also did a bit of housekeeping (because I wanted to use Go 1.22 range-over-int, which needed several other updates)

[fische]

Are we expecting more than a few events for a given action? If not, could we just make those channels buffered?

[peterebden]

Don't the workers send a periodic update once a minute or so?

[peterebden]

We could also get rid of that, or just have a buffer size of like 100 and deal with it if they fill up

[fische]

Don't the workers send a periodic update once a minute or so?

Just had a quick look at the worker code and it looks like it only publishes when Executing and when Completed.

We could also get rid of that, or just have a buffer size of like 100 and deal with it if they fill up

Yeah we could even do that