Updated MySQL to show setting is deprecated (#8137)

* Updated MySQL to show setting is deprecated
* Update src/guides/v2.4/install-gde/prereq/mysql.md

Co-authored-by: Barny Shergold <[email protected]>
Co-authored-by: Margaret Eker <[email protected]>

Author: 3 people

src/guides/v2.3/install-gde/prereq/mysql.md

@@ -414,6 +414,12 @@ To configure a MySQL database instance:
 
    If this setting is not enabled, `setup:db:status` will always report that `Declarative Schema is not up to date`.
 
+{:.bs-callout-info}
+The `explicit_defaults_for_timestamp` setting is deprecated. This setting controls deprecated TIMESTAMP behaviors that will be removed in a future MySQL release.  When those behaviors are removed, the `explicit_defaults_for_timestamp` setting will be removed as well.
+
+{:.bs-callout-warning}
+On Magento projects deployed on the Cloud platform, the `explicit_defaults_for_timestamp` setting for MySQL (MariaDB) defaults to *OFF*
+
 {:.ref-header}
 Related topics
 

src/guides/v2.4/install-gde/prereq/mysql.md

@@ -182,6 +182,12 @@ To configure a MySQL database instance:
 
    If this setting is not enabled, `setup:db:status` will always report that `Declarative Schema is not up to date`.
 
+{:.bs-callout-info}
+The `explicit_defaults_for_timestamp` setting is deprecated. This setting controls deprecated TIMESTAMP behaviors that will be removed in a future MySQL release. When those behaviors are removed, the `explicit_defaults_for_timestamp` setting will be removed as well.
+
+{:.bs-callout-warning}
+On Magento projects deployed on the Cloud platform, the `explicit_defaults_for_timestamp` setting for MySQL (MariaDB) defaults to *OFF*
+
 {:.ref-header}
 Related topics