Use job middleware for queue job model updating

[lindyhopchris]

Laravel 6 introduced job middleware. Need to investigate whether this is a better way of implementing the updating of the queue job models, rather than the current implementation of binding to the queue events. The weakness of queue events is the having to unserialize the payload - i.e. there isn't direct access to the queue job model that is attached to the job itself.

[lindyhopchris]

Closing in favour of dealing with this in the new package.

[lindyhopchris]

Leaving this as a note...

I've looked into this and it isn't actually possible to use job middleware. This is because the middleware doesn't know for sure what the result of the job processing is - especially as it would depend where in the middleware stack the JSON:API middleware would run.

Currently we are bound to the job events. Although this is a little messy (because for example we need to deserialize the job again to get the client job model), it is the best place to know for sure what happened to the job and save the actual result into the database.