Move the notice related to the Oracle MySQL v8.x database warning / error just below the question in the FAQ so users can tell early.

FAQs.md

@@ -31,6 +31,9 @@ There is no release schedule for Vaultwarden. If the maintainers have time and t
 If you "want early access to the newest features, enhancements, or bug fixes" you can always switch to using the `testing` image, which is always based upon the newest commit. Cf. [Which container image to use](https://github.com/dani-garcia/vaultwarden/wiki/Which-container-image-to-use)
 
 ## Can Vaultwarden connect to an Oracle MySQL V8.x database?
+
+**Note** This warning does not occur with Vaultwarden version 1.35.5 or later so change described below is no longer necessary after version 1.35.5, which supports 'caching_sha2_password'.
+
 It could happen that you get the following warning when trying to start Vaultwarden when using Oracle MySQL v8.x
 ```
 [vaultwarden::util][WARN] Can't connect to database, retrying: DieselConError.
@@ -51,8 +54,6 @@ ALTER USER 'vaultwarden'@'localhost' IDENTIFIED WITH mysql_native_password BY 'y
 ```
 Also see: [Using MariaDB - Create Database and User](https://github.com/dani-garcia/vaultwarden/wiki/Using-the-MariaDB-(MySQL)-Backend#create-database-and-user)
 
-This change is no longer necessary after version 1.35.5, which supports 'caching_sha2_password'.
-
 ## My client (Desktop, Mobile, Web) does not work, I can not login or it complains about invalid certificates.
 The Bitwarden clients need a secure connection to fully work without any issues. Though some clients can work without a secure connection we do not recommend this.  
 Most of the time when people are using certificates and still have issues, they are using so called Self-Signed certificates. While those could provide a secure connection, some platforms do not allow or support this.