[11.x] Auto-register commands in routes/console.php

[SamuelNitsche]

While working on route registration in a Laravel app, I noticed some inconvenience when using the using callback of the withRouting method.
In particular, the main issue was that commands defined in routes/console.php were not registered anymore. When checking the docs, I saw that there is a way to register commands using the withCommands method.

However, to achieve the same behaviour of the withRouting method you must pass the routes/console.php file as a parameter.
I think the DX could be improved by checking if the routes/console.php file exists and if so, registering all commands (including their schedule) automatically. This should be a good sensible default since the routes/console.php file is the default way to register commands in Laravel 11.

So before:

return Application::configure(basePath: dirname(__DIR__))
    ->withCommands([
        __DIR__ . 'routes/console.php',
    ]);

and after:

return Application::configure(basePath: dirname(__DIR__))
    ->withCommands();

I couldn't find any existing tests for the ApplicationBuilder so I decided to also not add any in this PR.

[rodrigopedra]

@taylorotwell when there are both commands in routes/console.php and app/Console/Commands this change only registers the commands in routes/console.php.

Luckily, I have a preparation Envoy script before deploying, as I never tested for a command availability.

[Cellard]

Schedules (php artisan schedule:list) are doubling now.

[crynobone]

@SamuelNitsche this PR has been reverted due to breaking change with existing application.