[5.5] Queue worker will pass connection + queue name to Looping event

[stierler]

Re-creating PR to master instead of 5.4, as requested by @taylorotwell
(I modified the previous - #18975 but couldn't reopen)

[laurencei]

What about the idea I mentioned on the other thread - modify WorkerOptions to have a copy/knowledge of connectionName and queue - then just pass WorkerOptions into the looping event?

This gives more options to people who want to hook into the loop event, so they can know sleep, timeout etc - rather than just two static variables.

And it makes sense for WorkerOptions to know the connectionName and queue anyway.