Multi Master Replication

### Description

I have 3 databases named 'wms_n' runting on 3 servers. Those databases are replicated to one server with database names rewrite. Database from server A is renames (by replication process) to be wms_A the same happens to to other databases.
Here example of the setup https://percona.community/blog/2018/09/10/multi-master-with-mariadb-10-tutorial/

The problem is that update statement has embedded database name and incorrect entry is written into bin log. Instead of
UPDATE wms_n.TABLE1 ...
we should have:
USE wms_n
UPDATE TABLE1

this way replication process can re-write the database name before the UPDATE statement.
Otherwise the replicated database reports error that wms_n database doesn't exists.

### DBeaver Version

Version 22.3.0.202212041619

### Operating System

macOS Ventura 13.0.1

### Database and driver

MariaDB 10.4.12

### Steps to reproduce

1. Setup Multi-Master replication as per (https://percona.community/blog/2018/09/10/multi-master-with-mariadb-10-tutorial/)
2. Update values in any of the tables on one of the master servers.

Expected behaviour value updated on replicated server (in renamed database)

Actual behaviour replication process reports that the database doesn't exists

### Additional context

_No response_