* Implemented 'SHOW WARNINGS' and 'SHOW COUNT(*) FROM WARNINGS' query handling.
* When a query produces warnings, the warning count is now included in the query response.

Additionally, a new variable 'mysql-query_cache_with_warnings_support' has been introduced for the query cache feature:

* A value of '0' means that if a query execution produces warnings, the resultset will not be saved in the query cache.
* A value of '1' indicates that if a query produces warnings, the resultset will be saved in the query cache, but the warning count in that resultset will be set to '0'.

** Note:
* Warning handling is dependent on the query digest and 'mysql-query_digests' must be enabled for it to work.
* Warnings saved in logfile ['mysql-log_mysql_warnings_enabled'] and the current feature can work in conjunction with each other.

…' to 'mysql-query_cache_handle_warnings'

* Introduced global variable 'mysql-handle_warnings' to control warning support in ProxySQL
* Included 'handling_warnings' flag in the 'mysql_hostgroup_attributes' table (hostgroup_settings). This flag holds top priority and can override the value of the global variable 'mysql_handle_warnings'.

* 'MySQL_Connection::warning_count' will be globally employed for managing multiplexing control and transmitting the warning count to the client
* Fixed prepare statement bug: When preparing, if the digest matches, the result set is retrieved from the cache and sent to the client.

Note:
Currently using 'mysql_warning_count' to retrieve the warning count for prepared statement.

… disabled.

* Introduced 'ps_type' enum to differentiate between preparing a statement and executing a statement
* Fixed issue where the warning count fails to reset when the SET statement generates a warning.
* Resolved the issue where the 'server_status' and 'warning count' were not accurately represented in the statement.
* Replaced 'mysql_warning_count' with 'mysql_stmt_warning_count' for retrieving the warning count in statements.
* Added 'handle_warning' field in hostgroup_attributes TAP test
* Updated warnings TAP test

…ent does not support CLIENT_DEPRECATE_EOF, warning_count will be '0' in intermediate EOF packet.

* Suppress the display of warning counts in the "SHOW WARNINGS" statement.

…d print it in the log. This override will apply to all TAP tests, except when the TAP test is linked with the MySQL client library (LIBMYSQL_HELPER defined).

* Avoid closing of same mysql connection twice on error.
* Disabled warning count logging on few TAP tests
* Enable CLIENT_DEPRECATE_EOF on 20% of total mysql connections

…final

# Conflicts:
#	test/tap/tests/set_testing-240-t.cpp