Update Known Issues docs to reflect fix for Database and LDAP Secrets Engine rotation issue (#30057)

* add note about upgrading

* typo

* Update website/content/partials/known-issues/database-skip-static-role-rotation.mdx

Co-authored-by: Sarah Chavis <[email protected]>

---------

Co-authored-by: Sarah Chavis <[email protected]>

Author: brewgator

website/content/partials/known-issues/1_19-failures-after-external-group-changes-standby.mdx

@@ -1,12 +1,12 @@
-### Login/token renewal failures after group changes (((#group-writes)))
+### Login/token renewal failures after group changes ((#group-writes))
 
 #### Affected Versions
-- 1.19.0 
+- 1.19.0
 
 #### Issue
-Performance standby nodes return a 500 error during login or token renewal if an 
-entity's external group association has changed. This occurs because standbys are 
+Performance standby nodes return a 500 error during login or token renewal if an
+entity's external group association has changed. This occurs because standbys are
 unable to persist the updated group membership to storage.
 
 #### Workaround
-Direct all logins and token renewals to the active node. 
+Direct all logins and token renewals to the active node.

website/content/partials/known-issues/database-skip-static-role-rotation.mdx

@@ -14,4 +14,5 @@ their passwords rotated when Vault is restarted. The password rotation will not
 occur on restart if the static role has already had its password rotated.
 
 #### Workaround
-Currently, there is no workaround except to avoid a restart of the backend.
+Upgrade to Vault version 1.18.6+ and 1.19.1+. For earlier versions of Vault, the only
+workaround avoiding restarts of the backend.