Update CI Know issue template to point to helper page and update docs (#99077)

* Update CI Know issue template to point to helper page and update docs

* Delete .github/ISSUE_TEMPLATE/04_ci_known_issue.yml

* Rename 05_blank_issue.md to 04_blank_issue.md

* Update failure-analysis.md

.github/ISSUE_TEMPLATE/04_ci_known_issue.yml

@@ -1,32 +0,0 @@
-name: CI Known Issue Report
-description: Create a known issue directly
-labels: ["blocking-clean-ci","Known Build Error"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Use this template to report issues currently affecting PR stability, be it build or test failures.
-  - type: textarea
-    id: background
-    attributes:
-      label: Error Blob
-      description: Please identify a clear error string that can help identify future instances of this issue. For more information on how to fill this check our issue triage guidelines at [Failure Analysis](/dotnet/runtime/blob/main/docs/workflow/ci/failure-analysis.md#what-to-do-if-you-determine-the-failure-is-unrelated)
-      value: |
-        ```json
-        {
-          "ErrorMessage": "",
-          "BuildRetry": false,
-          "ErrorPattern": "",
-          "ExcludeConsoleLog": true
-        }
-        ```
-    validations:
-      required: true
-  - type: textarea
-    id: repro-steps
-    attributes:
-      label: Reproduction Steps
-      description: |
-        If possible describe where you observe the issue with links and any other relevant details.
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -18,3 +18,6 @@ contact_links:
   - name: Issue with WPF
     url:  https://github.com/dotnet/wpf/issues/new/choose
     about: Please open issues relating to WPF in dotnet/wpf.
+  - name: CI Known Issue Report
+    url: https://helix.dot.net/BuildAnalysis/CreateKnownIssues
+    about: Use the helper to create a Known Issue in CI if failures in your runs are unrelated to your change. See [Failure Analysis](https://github.com/dotnet/runtime/blob/main/docs/workflow/ci/failure-analysis.md#what-to-do-if-you-determine-the-failure-is-unrelated) for triage instructions.

docs/workflow/ci/failure-analysis.md

@@ -91,6 +91,7 @@ If you have considered all the diagnostic artifacts and determined the failure i
     ````
     It already contains most of the essential information, but *it is very important that you fill out the json blob*.
 
+    - You can now use the [Build Analysis Known Issue Helper](https://helix.dot.net/BuildAnalysis/CreateKnownIssues) to create an issue. It assists in adding the right set of labels, fill the necessary paths in the json blob, and it will validate that it matches the text presented for the issue found in the logs.
     - You can add into the `ErrorMessage` field the string that you found uniquely identifies the issue. In case you need to use a regex, use the `ErrorPattern` field instead. This is a limited to a single-line, non-backtracking regex as described [here](https://github.com/dotnet/arcade/blob/main/Documentation/Projects/Build%20Analysis/KnownIssues.md#regex-matching). This regex also needs to be appropriately escaped. Check the [arcade known issues](https://github.com/dotnet/arcade/blob/main/Documentation/Projects/Build%20Analysis/KnownIssues.md#filling-out-known-issues-json-blob) documentation for a good guide on proper regex and JSON escaping.
     - The field `ExcludeConsoleLog` describes if the execution logs should be considered on top of the individual test results. **For most cases, this should be set to `true` as the failure will happen within a single test**. Setting it to `false` will mean all failures within an xUnit set of tests will also get attributed to this particular error, since there's one log describing all the problems. Due to limitations in Known Issues around rate limiting and xUnit resiliency, setting `ExcludeConsoleLog=false` is necessary in two scenarios:
       + Nested tests as reported to Azure DevOps. Essentially this means theory failures, which look like this when reported in Azure DevOps: ![xUnit theory seen in azure devops](theory-azdo.png).