Add scenario for Jira Connect proxy logs

What does this MR do?

This MR does the following:

• Adds a saved search for Kibana with all of the fields that we are wanting to look at preselected so Support Engineers can just enter in the correlation ID (for productivity)
• Adds a second scenario where GitLab actually throws an exception if it cannot connect to the self-managed instance
• Expands on the first scenario when GitLab did attempt to contact the self-managed instance

Related issues

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • Ensure a release milestone is set.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.

doc/administration/settings/jira_cloud_app_troubleshooting.md

@@ -136,7 +136,8 @@ The GitLab Support team can then look up why this is failing in the GitLab.com s
 NOTE:
 These steps can only be completed by GitLab Support.
 
-[In Kibana](https://log.gprd.gitlab.net/app/r/s/0FdPP), the logs should be filtered for `json.meta.caller_id: JiraConnect::InstallationsController#update` and `NOT json.status: 200`.
+[In Kibana](https://log.gprd.gitlab.net/app/r/s/0FdPP), the logs should be filtered for
+`json.meta.caller_id: JiraConnect::InstallationsController#update` and `NOT json.status: 200`.
 If you have been provided the `X-Request-Id` value, you can use that against `json.correlation_id` to narrow down the results.
 
 Each `GET` request to the Jira Connect Proxy URL `https://gitlab.com/-/jira_connect/installations` generates two log entries.
@@ -146,17 +147,17 @@ For the first log:
 - `json.status` is `422`.
 - `json.params.value` should match the GitLab self-managed URL `[[FILTERED], {"instance_url"=>"https://gitlab.example.com"}]`.
 
-For the second log there are two different scenarios you may observe:
+For the second log, you might have one of the following scenarios:
 
 - Scenario 1
-  - `json.message`, `json.jira_status_code` and `json.jira_body` is present
+  - `json.message`, `json.jira_status_code`, and `json.jira_body` are present.
   - `json.message` is `Proxy lifecycle event received error response` or similar.
-  - `json.jira_status_code` and `json.jira_body` may contain the response received from the self-managed instance or a proxy in front of the self-managed instance
+  - `json.jira_status_code` and `json.jira_body` might contain the response received from the self-managed instance or a proxy in front of the instance.
   - If `json.jira_status_code` is `401` and `json.jira_body` is empty, [**Jira Connect Proxy URL**](jira_cloud_app.md#set-up-your-instance) might not be set to
   `https://gitlab.com`.
 - Scenario 2
-  - `json.exception.class` and `json.exception.message` is present
-  - `json.exception.class` and `json.exception.message` will detail if there was an issue contacting the self-managed instance
+  - `json.exception.class` and `json.exception.message` are present.
+  - `json.exception.class` and `json.exception.message` contain whether an issue occurred while contacting the self-managed instance.
 
 ## Error when connecting the app