Update analyzer doc pages for special treatments regarding MSTestAnalysisMode

Author: Youssef1313

docs/core/testing/mstest-analyzers/includes/disabled-in-all.md

@@ -0,0 +1,2 @@
+> [!NOTE]
+> This rule is opt-in. It's not enabled even when using `<MSTestAnalysisMode>All</MSTestAnalysisMode>`. For more information about `MSTestAnalysisMode`, see [MSTest code analysis](../overview.md).

docs/core/testing/mstest-analyzers/mstest0003.md

@@ -16,16 +16,16 @@ dev_langs:
 ---
 # MSTEST0003: Test methods should have valid layout
 
-| Property                            | Value                                              |
-|-------------------------------------|----------------------------------------------------|
-| **Rule ID**                         | MSTEST0003                                         |
-| **Title**                           | Test methods should have valid layout              |
-| **Category**                        | Usage                                              |
-| **Fix is breaking or non-breaking** | Breaking                                           |
-| **Enabled by default**              | Yes                                                |
-| **Default severity**                | Warning                                            |
-| **Introduced in version**           | 3.2.0                                              |
-| **Is there a code fix**             | Yes                                                |
+| Property                            | Value                                                                                     |
+|-------------------------------------|------------------------------------------------------------------------------------------|
+| **Rule ID**                         | MSTEST0003                                                                               |
+| **Title**                           | Test methods should have valid layout                                                    |
+| **Category**                        | Usage                                                                                    |
+| **Fix is breaking or non-breaking** | Breaking                                                                                 |
+| **Enabled by default**              | Yes                                                                                      |
+| **Default severity**                | Warning (escalated to Error when setting `MSTestAnalysisMode` to `Recommended` or `All`) |
+| **Introduced in version**           | 3.2.0                                                                                    |
+| **Is there a code fix**             | Yes                                                                                      |
 
 ## Cause
 

docs/core/testing/mstest-analyzers/mstest0015.md

@@ -40,6 +40,8 @@ Ensure that the test method isn't ignored.
 
 Do not suppress a warning from this rule. If you ignore this rule, test method will be ignored.
 
+[!INCLUDE [disabled-in-all](includes/disabled-in-all.md)]
+
 ## Suppress a warning
 
 If you just want to suppress a single violation, add preprocessor directives to your source file to disable and then re-enable the rule.

docs/core/testing/mstest-analyzers/mstest0019.md

@@ -40,6 +40,8 @@ Replace the constructor call with a `[TestInitialize]` method.
 
 You usually don't want to suppress warnings from this rule if you decided to opt-in for it.
 
+[!INCLUDE [disabled-in-all](includes/disabled-in-all.md)]
+
 ## Suppress a warning
 
 If you just want to suppress a single violation, add preprocessor directives to your source file to disable and then re-enable the rule.

docs/core/testing/mstest-analyzers/mstest0020.md

@@ -40,6 +40,8 @@ Replace `[TestInitialize]` returning `void` by constructors.
 
 You usually don't want to suppress warnings from this rule if you decided to opt-in for it.
 
+[!INCLUDE [disabled-in-all](includes/disabled-in-all.md)]
+
 ## Suppress a warning
 
 If you just want to suppress a single violation, add preprocessor directives to your source file to disable and then re-enable the rule.

docs/core/testing/mstest-analyzers/mstest0021.md

@@ -40,6 +40,8 @@ Replace `[TestCleanup]` method by `Dispose` or `DisposeAsync` pattern.
 
 You usually don't want to suppress warnings from this rule if you decided to opt-in for it.
 
+[!INCLUDE [disabled-in-all](includes/disabled-in-all.md)]
+
 ## Suppress a warning
 
 If you just want to suppress a single violation, add preprocessor directives to your source file to disable and then re-enable the rule.

docs/core/testing/mstest-analyzers/mstest0022.md

@@ -40,6 +40,8 @@ Replace `Dispose` or `DisposeAsync` methods with `[TestCleanup]`.
 
 You usually don't want to suppress warnings from this rule if you decided to opt-in for it.
 
+[!INCLUDE [disabled-in-all](includes/disabled-in-all.md)]
+
 ## Suppress a warning
 
 If you just want to suppress a single violation, add preprocessor directives to your source file to disable and then re-enable the rule.