[Console][Messenger] add RunCommandMessage and RunCommandMessageHandler

[kbond]

Q	A
Branch?	6.3
Bug fix?	no
New feature?	yes
Deprecations?	no
Tickets	n/a
License	MIT
Doc PR	todo

Similar to #49813, when using the scheduler it could be useful to execute commands.

Usage

use Symfony\Component\Console\Exception\RunCommandFailedException;
use Symfony\Component\Console\Messenger\RunCommandMessage;

try {
    $context = $bus->dispatch(new RunCommandMessage('my:command'));

    $context->output; // string - output of command
    $context->exitCode; // int - the exit code
catch(RunCommandFailedException $e) { // if exit code is non-zero or command threw exception
    $e->context->output; // string - output of command
    $e->context->exitCode; // int - the exit code
    $e->getPrevious(); // null|\Throwable exception command threw if applicable
}

// "never" fail
$context = $bus->dispatch(new RunCommandMessage('my:command', throwOnNonSuccess: false, catchExceptions: true));

TODO:

• wire up
• tests

[kbond]

Like #49813 (comment), maybe CommandMessage and CommandMessageHandler would be better names?

[kbond]

Should I clone the application here instead of having the service not-shared?

[ro0NL]

maybe try/finally to modify state on the shared service?

[kbond]

I don't think I can do this as there's no way to access the current state of Application::$catchExceptions.

[kbond]

One thing I think is missing: making the output available if there's an exception. Consider a system that tracks messages and emails an admin on failure. I can attest that this is valuable information.

What about wrapping the caught exception in a new CommandFailedException that contains the output?

In #49813 this is possible because the thrown exception (ProcessFailedException) includes the Process instance which makes the output available.

[ro0NL]

see also #49813 (comment)

[ro0NL]

maybe try/finally to modify state on the shared service?

[kbond]

I've updated this PR:

1. Renamed the message to RunCommandMessage.
2. Added RunCommandContext to be returned from the handler
3. Added RunCommandFailedException that's thrown on failure that wraps the original exception and contains RunCommandContext
4. Configuration for throwing RunCommandFailedException on non-successful exit codes

(updated PR description to show usage)

[fabpot]

LGTM, @kbond I've made a rename suggestion.

[fabpot]

Thank you @kbond.