(latest/edge) prometheus-relation-joined hook can cause a mysql error during deployment

During the deployment of a cluster in the gate, there is a race-hazard error when the prometheus-relation-joined hook can result in a mysql error in the `create_user` method.

The issue is basically that if a transaction is attempted (with a commit) whilst the cluster is recovering Group Replication, then that commit will hard fail with the following error:

    MySQLdb.OperationalError: (3100, "Error on observer while running replication hook 'before_commit'.")

The trace from the error.log file provides more details:

2023-04-22T07:59:58.834202Z 0 [System] [MY-011565] [Repl] Plugin group_replication reported: 'Setting super_read_only=ON.'
2023-04-22T07:59:58.834268Z 0 [Warning] [MY-013469] [Repl] Plugin group_replication reported: 'This member will start distributed recovery using clone. It is due to the num
ber of missing transactions being higher than the configured threshold of 1.'
2023-04-22T07:59:59.836244Z 0 [System] [MY-013471] [Repl] Plugin group_replication reported: 'Distributed recovery will transfer data using: Cloning from a remote group don
or.'
2023-04-22T07:59:59.837981Z 0 [System] [MY-011503] [Repl] Plugin group_replication reported: 'Group membership changed to 172.16.0.174:3306, 172.16.0.245:3306, 172.16.0.101
:3306 on view 16821495149807797:5.'
2023-04-22T07:59:59.840913Z 38 [System] [MY-011566] [Repl] Plugin group_replication reported: 'Setting super_read_only=OFF.'
2023-04-22T08:00:00.285589Z 39 [Warning] [MY-013460] [InnoDB] Clone removing all user data for provisioning: Started
2023-04-22T08:00:00.550852Z 39 [Warning] [MY-013460] [InnoDB] Clone removing all user data for provisioning: Finished
2023-04-22T08:00:01.404748Z 41 [ERROR] [MY-011600] [Repl] Plugin group_replication reported: 'Transaction cannot be executed while Group Replication is recovering. Try agai
n when the server is ONLINE.'

Essentially, what seems to be happening is that the prometheus-relation-joined hook fires quickly after the vault-relation-joined which had caused the instance to change from not TLS to TLS (using the cert from vault) and this had caused group replication to be restarted.

Possible solution:
------------------

The solution is to retry the commit if the 3100 error occurs several times (to allow Group Replication to finish) and then just return False so that the handler will try again on the next hook execution. This would allow the unit to recover gracefully from the error.