[SPARK-47172][DOCS][FOLLOWUP] Fix spark.network.crypto.ciphersince ve…

…rsion field on security page

### What changes were proposed in this pull request?

Given that SPARK-47172 was an improvement but got merged into 3.4/3.5, we need to fix the since version to eliminate misunderstandings.

### Why are the changes needed?

doc fix

### Does this PR introduce _any_ user-facing change?

no

### How was this patch tested?

doc build

### Was this patch authored or co-authored using generative AI tooling?
no

Closes #47353 from yaooqinn/SPARK-47172.

Authored-by: Kent Yao <yao@apache.org>
Signed-off-by: Kent Yao <yao@apache.org>
(cherry picked from commit d8820a0)
Signed-off-by: Kent Yao <yao@apache.org>

docs/security.md

@@ -168,7 +168,7 @@ The following table describes the different options available for configuring th
     Cipher mode to use. Defaults "AES/CTR/NoPadding" for backward compatibility, which is not authenticated. 
     Recommended to use "AES/GCM/NoPadding", which is an authenticated encryption mode.
   </td>
-  <td>4.0.0</td>
+  <td>4.0.0, 3.5.2, 3.4.4</td>
 </tr>
 <tr>
   <td><code>spark.network.crypto.authEngineVersion</code></td>