[10.x] Add serializeAndRestore() to QueueFake andBusFake

[cosmastech]

Some context

• I have ruined a lot of people's day by submitting this PR on spatie's medialibrary which did not test that the model could be properly serialized/unserialized.
• An issue like this is not detectable until we actually test explicitly for the serialization/unserialization

---

Queues are awesome. Jobs are awesome. Faking within tests is awesome.

But testing that a job is pushed is not always enough. Nor is testing the job's properties match expected values.

The normal process for jobs is that they are pushed to the queue where they are serialized and deserialized when they are run by a worker process. If there is an issue trying to serialize an object for your queue, it will fail... but probably not within your test suite 😟

Take for instance this job:

class MyJob implements ShouldQueue
{
    use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;

    public function __construct(public $value) {}
}

If we write a unit test like:

public function testCanDispatchJob()
{
    Queue::fake();
    MyJob::dispatch(fn() => true);
    Queue::assertDispatched(MyJob::class, fn($job) => $job->value instanceof \Closure); ✅ 
}

We see no problem in our test suite so it gets approved and merged... but then we release it into production and all of these jobs fail to serialize.

Instead, now we can write our tests to leverage QueueFake@serializeAndRestoreJobs(). This simulates the queuing process insofar that we will call serialize() and unserialize() on the job.

public function testCanDispatchJobImproved()
{
    Queue::fake()->serializeAndRestore();

    MyJob::dispatch(fn() => true); // ❌ Exception  Serialization of 'Closure' is not allowed. 🥳 
}

---

Will gladly add a PR(s) for this to be added to EventFake and BusFake.

[taylorotwell]

Can you add to Bus as well and mark as ready for review?

[cosmastech]

Can you add to Bus as well and mark as ready for review?

@taylorotwell Done.

I know that you moved the logic out of the trait I had originally created. My two cents is that it would be a lot cleaner to leave it as a trait rather than duplicating the code in BusFake && QueueFake. I can make that change if you agree.

Also, not sure if we want to add this for EventFake as well?