[7.x] Fix Console expectation assertion order

[nuernbergerA]

This PR solves the ordering bug when using command and other assertions in the same test.

Please find more detailed information in issue #32256

Current State

Laravel command assertions (expectations) are being run before the application gets destroyes.
This is why command assertions alwaysrun at the end of the test and not in the provided order inside the test.

Solution

This PR changes the implementation so that the command assertions run immediately after defining them.
Fixes #32256.

[jasonmccreary]

@nuernbergerA, I thought you had to chain the command setup with run or execute. Is this now different?

[nuernbergerA]

@jasonmccreary short answer: it should all run as before, except that failing questions fail in the expected order.

execute() is an alias for run() which is called on __destruct()

All I/O related assertions have been registered on this hook which was called here

Let's take @christophrumpel example

public function it_imports_users_to_the_database(): void
{
    //expectsQuestion() registers callback on TestCase
    $this->artisan('import:users')
            ->expectsQuestion('Please provide the URL to import users:', 'https://myapi.com/users')
            //PendingCommand calls __destruct() / run()
            ->assertExitCode(0);

    //This evaluates immediately
    $this->assertCount(100, User::all());

   //TestCase::tearDown()
   //executes previous defined callback
}

So the only change is that if an expectedQuestion() wasn't asked it failed before it evaluates assertCount()

I hope my attempt to illustrate the issue didn't confuse you.