Update repository visibility changes to be relevant for GHES location

[janbrasna]

Why:

Visibility changes should no longer refer to dotcom in GHES case.

Closes #35262

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

{% data variables.product.prodname_dotcom_the_website %}
to
{% data variables.location.product_location %}

effectively keeping the current wording for fpt/ghec:

Changing from internal to public

• The code will be visible to everyone who can visit GitHub.com.

and making the output for ghes read:

Changing from private to public

• The code will be visible to everyone who can visit your GitHub Enterprise Server instance.

https://docs-35282-f0afae.preview.ghdocs.com/en/enterprise-cloud@latest/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility#changing-from-internal-to-public
vs.
https://docs-35282-f0afae.preview.ghdocs.com/en/[email protected]/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility#changing-from-private-to-public

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

  • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

• For content changes, I have completed the self-review checklist.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10

---

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

[nguyenalex836]

Howdy @janbrasna! 👋 I'm going to wait a few days to see if @sparrowt wants to open a PR with this update, as they first discovered this issue.

If they haven't submitted a PR by early next week, we can get this merged 💛