WithoutDbalTransaction attribute: possibility dot not wrap specific async endpoint or command handler in transaction

[lifinsky]

Description
Command handlers or asynchronous endpoints are used only to send commands to other services or simply do not store anything in the database and obviously would like to avoid running a transaction on a specific endpoint.

Example

#[Asynchronous("db")]
#[EventHandler(endpointId: "notify")]
#[WithoutDbalTransaction]
public function notify(OrderWasPlaced $event) : void
{
    // distributed bus call
}

[dgafka]

That would not be feasible to do it on the Handler level, because transaction is already started at that point.
However you can already set up a Message Consumer without transactions:

    DbalConfiguration::createWithDefaults()
        ->withoutTransactionOnAsynchronousEndpoints(["db"]

[lifinsky]

@dgafka I know, but unfortunately at the service level there are usually three consumers (distributed, db and async internal) and for outbox (db + async internal) not all db channels can be without a transaction

[lifinsky]

Sometimes, instead of selectively adding a transaction block using the DbalTransaction attribute, it is easier to selectively disable it.

[lifinsky]

For example, we use db channel for ditributed bus call, where transaction is not needed.