Update sonarlint.plugin.api.version to v10.27.0.81966 (#5602)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Michal Zgliczynski <[email protected]>

Author: renovate[bot]

pom.xml

@@ -74,7 +74,7 @@
     <gson.version>2.13.1</gson.version>
     <analyzer-commons.version>2.18.0.3393</analyzer-commons.version>
     <sslr.version>1.24.0.633</sslr.version>
-    <sonarlint.plugin.api.version>10.26.0.81748</sonarlint.plugin.api.version>
+    <sonarlint.plugin.api.version>10.27.0.81966</sonarlint.plugin.api.version>
 
     <artifactsToPublish>${project.groupId}:sonar-javascript-plugin:jar</artifactsToPublish>
     <maven.test.redirectTestOutputToFile>true</maven.test.redirectTestOutputToFile>
@@ -153,6 +153,11 @@
         <artifactId>commons-lang</artifactId>
         <version>2.6</version>
       </dependency>
+      <dependency>
+        <groupId>org.apache.commons</groupId>
+        <artifactId>commons-lang3</artifactId>
+        <version>3.18.0</version>
+      </dependency>
       <dependency>
         <groupId>org.sonarsource.sslr</groupId>
         <artifactId>sslr-core</artifactId>

sonar-plugin/javascript-checks/src/main/resources/org/sonar/l10n/javascript/rules/javascript/S4426.html

@@ -16,9 +16,9 @@ <h2>Why is this an issue?</h2>
 <p>Note that depending on the algorithm, the term <strong>key</strong> refers to a different mathematical property. For example:</p>
 <ul>
   <li> For RSA, the key is the product of two large prime numbers, also called the <strong>modulus</strong>. </li>
-  <li> For AES and Elliptic Curve Cryptography (ECC), the key is only a sequence of randomly generated bytes.
+  <li> For Elliptic Curve Cryptography (ECC), the key is only a sequence of randomly generated bytes.
     <ul>
-      <li> In some cases, AES keys are derived from a master key or a passphrase using a Key Derivation Function (KDF) like PBKDF2 (Password-Based Key
+      <li> In some cases, keys are derived from a master key or a passphrase using a Key Derivation Function (KDF) like PBKDF2 (Password-Based Key
       Derivation Function 2) </li>
     </ul>  </li>
 </ul>
@@ -139,11 +139,6 @@ <h4>RSA (Rivest-Shamir-Adleman) and DSA (Digital Signature Algorithm)</h4>
 <p>The security of these algorithms depends on the difficulty of attacks attempting to solve their underlying mathematical problem.</p>
 <p>In general, a minimum key size of <strong>2048</strong> bits is recommended for both. It provides 112 bits of security. A key length of
 <strong>3072</strong> or <strong>4096</strong> should be preferred when possible.</p>
-<h4>AES (Advanced Encryption Standard)</h4>
-<p>AES supports three key sizes: 128 bits, 192 bits and 256 bits. The security of the AES algorithm is based on the computational complexity of trying
-all possible keys.<br> A larger key size increases the number of possible keys and makes exhaustive search attacks computationally infeasible.
-Therefore, a 256-bit key provides a higher level of security than a 128-bit or 192-bit key.</p>
-<p>Currently, a minimum key size of <strong>128 bits</strong> is recommended for AES.</p>
 <h4>Elliptic Curve Cryptography (ECC)</h4>
 <p>Elliptic curve cryptography is also used in various algorithms, such as ECDSA, ECDH, or ECMQV. The length of keys generated with elliptic curve
 algorithms is mentioned directly in their names. For example, <code>secp256k1</code> generates a 256-bits long private key.</p>