* Added separate fetching of mysql_server_incoming and runtime_mysql_server records based on algorithm selection.
* Few memory leaks fix
* Code refactoring

* Changed commit signature.
* Few fixes

* Few issues fixed

* Fetching mysql_servers_v2 records from admin
* Added comments.

* Added detailed comments.

…ed ahead of the 'mysql_servers' code block. This ensures that the most recent value of 'admin-cluster_mysql_servers_sync_algorithm' is available in mysql_servers sync.

* Reset global checksum if 'admin-cluster_mysql_servers_sync_algorithm' is changed.

…sql_servers' and 'mysql_servers_v2' across all nodes. The test involves creating two replica nodes, one with a monitor enabled and the other with a monitor disabled. The test verifies that the correct records are synced among these nodes based on the value of 'admin-cluster_mysql_servers_sync_algorithm'.

* Cleared duplicate code.
* Added comments

…se."

* In the event of any failure, it's crucial to call the cleanup function to prevent any orphaned replica instances from remaining active.

…_mysql_servers

# Conflicts:
#	include/ProxySQL_Cluster.hpp
#	include/proxysql_admin.h
#	lib/MySQL_HostGroups_Manager.cpp
#	lib/ProxySQL_Admin.cpp
#	lib/ProxySQL_Cluster.cpp

…_mysql_servers

…hange is triggered from monitoring module

…_mysql_servers

# Conflicts:
#	lib/MySQL_HostGroups_Manager.cpp

…ers' into v2.x_refactor_cluster_mysql_servers

…_mysql_servers_final

# Conflicts:
#	lib/MySQL_HostGroups_Manager.cpp
#	lib/ProxySQL_Cluster.cpp

TODO:
Update documentation: mysql_servers_v2

If these resultsets are not updated, checksums will always mismatch
between the peer cluster nodes in case servers are deleted. The primary
will hold the correct checksum ('0x0'), but will report the old resultset
to the peer node, the second will compute a checksum different than the
expected '0x0'. Cycle won't stop until config is updated in the target
primary.

- Resultsets for 'runtime_mysql_servers' and 'mysql_servers_v2' are now
  directly generated by the SQL query.
- Checksum computations are simplified to 'SQLite3_result::raw_checksum'
  and equivalent function 'mysql_raw_checksum'.

…cluster_mysql_servers

Config should only be used for checksum computation and cluster
resultset generation for 'LOAD MYSQL SERVERS TO RUNTIME'. Otherwise
user config ('main.mysql_servers') would be promoted at each 'commit'
call, and propagated through the cluster members.

If 'MySQL_HostGroups_Manager::incoming_mysql_servers' happens to be
empty when a 'CLUSTER_QUERY_MYSQL_SERVERS_V2' request is received in
Admin, since there wasn't any user config promoted to runtime yet, the
response should be an empty resulset.