WSREP GTID Sync Inconsistency Version 10.5.13 | Bionic & Focal

I am utilising 4 Independent Mariadb Clusters on Focal and Bionic.

Whilst running version 10.5.13 I am noticing inconsistencies with WSREP GTID synchronisation issues.
This is an issue as I have replica's replication from either one of the Multimaster nodes, but switch to a new timeline and can not recover due to the `gtid_binlog` position being different.

An example two instances within a cluster are:
```node2:
Variable_name Value
gtid_binlog_pos 2-2-268
gtid_binlog_state 2-2-268
gtid_cleanup_batch_size 64
gtid_current_pos 2-2-268
gtid_domain_id 203
gtid_ignore_duplicates OFF
gtid_pos_auto_engines
gtid_slave_pos
gtid_strict_mode OFF
wsrep_gtid_domain_id 2
wsrep_gtid_mode ON
node0:
Variable_name Value
gtid_binlog_pos 2-2-310
gtid_binlog_state 2-2-310
gtid_cleanup_batch_size 64
gtid_current_pos 2-2-310
gtid_domain_id 200
gtid_ignore_duplicates OFF
gtid_pos_auto_engines
gtid_slave_pos
gtid_strict_mode OFF
wsrep_gtid_domain_id 2
wsrep_gtid_mode ON```

I have verified the configurations for log_slave_updates, gtid_domain_id, server_id details are correct according to the documentation.

This bug feels very remnant of the Ticket MDEV-10227