MySqlConnector.MySqlException : XAER_RMFAIL on TransactionScope.Dispose()

[PatrickMNL]

Software versions
MySqlConnector version: 2.4.0
Server type (MySQL, MariaDB, Aurora, etc.) and version: MariaDB 11.8.3
.NET version: 8.0

Describe the bug
When running into a deadlock, in the following scenario;

T1 - XA START
T2 - XA START
T1 - XA END
T1 - XA PREPARE
T1 - XA COMMIT
T2 - Deadlock Exception (aborting the transaction, disposing the TransactionScope)
T2 - XA PREPARE

MariaDB 11.8.3 returns the following exception;

MySqlConnector.MySqlException : XAER_RMFAIL: The command cannot be executed when global transaction is in the  ROLLBACK ONLY state
   at MySqlConnector.Core.ServerSession.ReceiveReplyAsync(IOBehavior ioBehavior, CancellationToken cancellationToken) in /_/src/MySqlConnector/Core/ServerSession.cs:line 885
   at MySqlConnector.Core.ResultSet.ReadResultSetHeaderAsync(IOBehavior ioBehavior) in /_/src/MySqlConnector/Core/ResultSet.cs:line 37
   at MySqlConnector.MySqlDataReader.ActivateResultSet(CancellationToken cancellationToken) in /_/src/MySqlConnector/MySqlDataReader.cs:line 130
   at MySqlConnector.MySqlDataReader.InitAsync(CommandListPosition commandListPosition, ICommandPayloadCreator payloadCreator, IDictionary`2 cachedProcedures, IMySqlCommand command, CommandBehavior behavior, Activity activity, IOBehavior ioBehavior, CancellationToken cancellationToken) in /_/src/MySqlConnector/MySqlDataReader.cs:line 482
   at MySqlConnector.Core.CommandExecutor.ExecuteReaderAsync(CommandListPosition commandListPosition, ICommandPayloadCreator payloadCreator, CommandBehavior behavior, Activity activity, IOBehavior ioBehavior, CancellationToken cancellationToken) in /_/src/MySqlConnector/Core/CommandExecutor.cs:line 56
   at MySqlConnector.MySqlCommand.ExecuteNonQueryAsync(IOBehavior ioBehavior, CancellationToken cancellationToken) in /_/src/MySqlConnector/MySqlCommand.cs:line 309
   at MySqlConnector.Core.XaEnlistedTransaction.ExecuteXaCommand(String statement) in /_/src/MySqlConnector/Core/XaEnlistedTransaction.cs:line 50
   at MySqlConnector.Core.XaEnlistedTransaction.OnRollback(Enlistment enlistment) in /_/src/MySqlConnector/Core/XaEnlistedTransaction.cs:line 36
   at MySqlConnector.Core.EnlistedTransactionBase.System.Transactions.IEnlistmentNotification.Rollback(Enlistment enlistment) in /_/src/MySqlConnector/Core/EnlistedTransactionBase.cs:line 47
   at System.Transactions.VolatileEnlistmentAborting.EnterState(InternalEnlistment enlistment)
   at System.Transactions.TransactionStateAborted.EnterState(InternalTransaction tx)
   at System.Transactions.Transaction.Rollback()
   at System.Transactions.TransactionScope.InternalDispose()
   at System.Transactions.TransactionScope.Dispose()

Because this is currently not handled, the application fails to recover and properly clean up the XA transaction, leaving it in place till the connection is aborted.

If T2 calls XA ROLLBACK after the above exception, the state is properly cleaned up.

Exception
See above ^

Expected behavior
There is no way of knowing that the server did put the transaction in a ROLLBACK ONLY state, calling XA END is the logical thing to do, however in this server version that returns the above exception. In the exception it at least makes us aware of the XA state, and we should thus call XA ROLLBACK when encountering this scenario.

[PatrickMNL]

When adding #1586, the XA transaction is properly cleaned up and our tests run successfully again.