Adding .ghe support ticket creation steps

[adamrr724]

Why:

Closes: https://github.com/github/docs-content/issues/19210

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
support/contacting-github-support/creating-a-support-ticket.md	fpt ghec ghes@ 3.17 3.16 3.15 3.14	fpt ghec ghes@ 3.17 3.16 3.15 3.14

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Copilot]

Pull Request Overview

This PR adds specific instructions for users with Data Residency or Enterprise Managed Users (EMU) accounts to the support ticket creation documentation. The change provides a clear step-by-step process for signing in with .ghe accounts, which was previously missing from the documentation.

• Adds detailed sign-in instructions for users with enterprise-managed accounts ending in .ghe
• Provides guidance on entering enterprise/tenant names and completing SAML authentication

[Copilot]

The hardcoded text 'Data Residency' and 'Enterprise Managed Users' should use variables instead. Check data/variables/enterprise.yml for existing variables like {% data variables.enterprise.prodname_managed_user %} for managed user accounts, or define new variables if they don't exist.