Add configuration section and sorted based on usefulness

Why is this change being made?

This is handbook update to the https://handbook.gitlab.com/handbook/support/workflows/saas_sm_cheatsheet/ to add some details about how instance are configured, and sorted the table in order of how it could be more useful.

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

This MR adjusts the SaaS, Self-Managed and Dedicated Troubleshooting tables to:

• add a section on configuration information
• sort the various sections based on usefulness

The need for this MR came up during our Brie & Gerardo's Office Hours: gitlab-com/support/support-pairing#11273.

This MR should make it easier for Support Engineers to get information about how various customers have configured their instances and makes the page more useful overall.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

---