Docs: Clarify plugin versioning known issue (hashicorp#17799)

website/content/docs/upgrading/upgrade-to-1.12.x.mdx

@@ -30,10 +30,13 @@ longer being available.
 
 To check whether a mount path is affected, read the tune information, or the
 database config. The affected plugins are `snowflake-database-plugin@v0.6.0+builtin`
-and any plugins with `+builtin.vault` metadata in their version. In this example,
-both mounts are affected because `plugin_version` is explicitly set and is one of
-the affected versions. All mounts where the version was omitted, or the plugin is
-external (regardless of whether the version was specified) are unaffected.
+and any plugins with `+builtin.vault` metadata in their version.
+
+In this example, the first two mounts are affected because `plugin_version` is
+explicitly set and is one of the affected versions. The third mount is not
+affected because it only has `+builtin` metadata, and is not the Snowflake
+database plugin. All mounts where the version is omitted, or the plugin is
+external (regardless of whether the version is specified) are unaffected.
 
 -> **NOTE:** Make sure you use Vault CLI 1.12.0 or later to check mounts.
 
@@ -50,6 +53,12 @@ Key                                   Value
 ...
 plugin_name                           snowflake-database-plugin
 plugin_version                        v0.6.0+builtin
+
+$ vault read sys/auth/kubernetes/tune
+Key                  Value
+---                  -----
+...
+plugin_version       v0.14.0+builtin
 ```
 
 As it is not currently possible to unset the plugin version, there are 3 possible