Update known issue cumulativeupdate18

Working on a support case (Case 2504010050001670, for reference) we have discovered that the same issue introduced in SQL Server 2019 CU14 is still present in SQL Server 2022 and it was not fixed. The workaround is still to enable the trace flags. Adding this info to the known issues

Author: bcaetano1997

support/sql/releases/sqlserver-2022/cumulativeupdate18.md

@@ -23,9 +23,11 @@ This article describes Cumulative Update package 18 (CU18) for Microsoft SQL Ser
 
 ## Known issues in this update
 
-SQL Server 2019 CU14 introduced a fix 14307204 to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT. However, this fix might create access violation dump files when the SESSION is reset for reuse (which is still present on SQL Server 2022). To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in SESSION_CONTEXT. To do this, use the following trace flags:
-	• 11042 - This trace flag disables the parallelism for the built-in SESSION_CONTEXT.
-  • 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+**Access violation when session is reset**   
+ 
+The following applies to SQL Server 2022 as well: 
+ 
+[!INCLUDE [av-sesssion-context-2019](../includes/av-sesssion-context-2019.md)]
 
 
 ## Improvements and fixes included in this update