Minor, update doc on -Xsanitize-parentheses

The ASM issue with parentheses was fixed in
https://gitlab.ow2.org/asm/asm/commit/02f00c4a82d9252b34d08dad47c540309fda3b7e

 #KT-29475

compiler/testData/cli/jvm/extraHelp.out

@@ -49,8 +49,8 @@ where advanced options include:
   -Xno-param-assertions      Don't generate not-null assertions on parameters of methods accessible from Java
   -Xno-receiver-assertions   Don't generate not-null assertion for extension receiver arguments of platform types
   -Xsanitize-parentheses     Transform '(' and ')' in method names to some other character sequence.
-                             This mode can BREAK BINARY COMPATIBILITY and is only supposed to be used as a workaround
-                             of an issue in the ASM bytecode framework. See KT-29475 for more details
+                             This mode can BREAK BINARY COMPATIBILITY and is only supposed to be used to workaround
+                             problems with parentheses in identifiers on certain platforms
   -Xscript-resolver-environment=<key=value[,]>
                              Script resolver environment in key-value pairs (the value could be quoted and escaped)
   -Xsingle-module            Combine modules for source files and binary dependencies into a single module

compiler/testData/codegen/box/mangling/parentheses.kt

@@ -1,10 +1,7 @@
 // !SANITIZE_PARENTHESES
 // IGNORE_BACKEND: JS, JS_IR
 
-// Sanitization is needed here because of an ASM bug: https://gitlab.ow2.org/asm/asm/issues/317868
-// As soon as that bug is fixed and we've updated to the new version of ASM, this test will start to pass without sanitization.
-// At that point, we should remove the -Xsanitize-parentheses compiler argument.
-// Also don't forget to disable this test on Android where parentheses are not allowed in names
+// Sanitization is needed here because DxChecker reports ParseException on parentheses in names.
 
 class `()` {
     fun `()`(): String {