[8.x] Clean up custom Queue payload between tests

[deleugpn]

When executing tests with Data Providers, Queue::createPayloadUsing leaks between tests and accumulates callbacks from different environments, leading to unexpected behaviors.

This pull request adds a clean up to the TearDown method so that callbacks are not kept between tests.
The test is likely to fail until orchestral/testbench-core#54 is merged as it mimics the same behavior for tests executed from within the framework.

[crynobone]

So it's not an issue if queue worker states persist between job (one worker may handle different jobs which might not related) and we only need to handle it between tests?

[deleugpn]

@crynobone The worker only bootstraps Laravel once and then can run as many job as necessary. The problem is that during tests, Laravel bootstraps and tears down once per test, but the tear down is not clearing the createPayloadUsing closures which leads to several closures being accumulated statically on the Queue::createPayloadUsing because the setUp is re-running all Service Providers.

I noticed this problem because the 1st test passes, but the 2nd fails. During the 2nd tests, there are 2 closures bound into the Queue::createPayloadUsing: 1 closure is the old container and 1 closure is the new container. The old container should have been cleared out and is not in a valid state anymore.

[taylorotwell]

Hey @deleugpn - we had to revert this due to some stuff in Telescope. An alternative might be calling Queue::createPayloadUsing(null) in the tearDown method of Laravel's base test case. We already reset some stuff there.