fix: Clarifying sources that support Terraform Dependency Updates

[CBID2]

Why:

This PR clarifies sources that support Terraform Dependency Updates. This change would help maintainers gain a better understanding on how to work with this feature.

Closes#8419

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

So far, I did the following:

Supported repositories and ecosystems" section of About Dependabot version updates

• Update the introduction to mention that dependencies in private registeries are also supported (similar to the mention of vendored dependencies).
• Update the link to the article with configuration options - link to both the #vendor anchor and also the #registries anchor.

"package-ecosystem" section of Configuration options for dependency updates

• Add a brief sentence, similar to that for vendor mentioning private registries and linking to registries.

"Configuration options for private registries" section of Configuration options for dependency updates

• Add a brief sentence to the first paragraph, mentioning that you can give Dependabot access to private package registries hosted by GitLab or Bitbucket by specifying a type of git and linking to git.

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

  • 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
code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md	fpt ghec ghes@ 3.113.103.93.83.7	fpt ghec ghes@ 3.113.103.93.83.7
code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md	fpt ghec ghes@ 3.113.103.93.83.7	fpt ghec ghes@ 3.113.103.93.83.7

---

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

[janiceilene]

Thanks so much for taking this on @CBID2! Let us know when you're ready for a review ⚡

[CBID2]

Thanks so much for taking this on @CBID2! Let us know when you're ready for a review ⚡

Hi @janiceilene. I'm struggling with this particular part:

"package-ecosystem" section of Configuration options for dependency updates

• Add a brief sentence, similar to that for vendor mentioning private registries and linking to registries.

I'm not sure what to put as a sentence and the Markdown issue that I'm having. Can you help me? :)

[mchammer01]

I'll take a look at this (probably tomorrow) ⚡

[am-stead]

👋 @CBID2,

I'm not sure what to put as a sentence and the Markdown issue that I'm having. Can you help me? :)

I think something like this would be sufficient?

If you want to allow {% data variables.product.prodname_dependabot %} to access a private package registry when performing a version update, you can include a registries setting in the configuration file. For more information, see [registries](#registries) below.

[CBID2]

👋 @CBID2,

I'm not sure what to put as a sentence and the Markdown issue that I'm having. Can you help me? :)

I think something like this would be sufficient?

If you want to allow {% data variables.product.prodname_dependabot %} to access a private package registry when performing a version update, you can include a registries setting in the configuration file. For more information, see [registries](#registries) below.

Made the edit @am-stead

[am-stead]

Hi @CBID2

I'm not seeing an edit / a File changed for this update?
(For the suggestion above)

"package-ecosystem" section of Configuration options for dependency updates

• Add a brief sentence, similar to that for vendor mentioning private registries and linking to registries.

[CBID2]

Hi @CBID2

I'm not seeing an edit / a File changed for this update?

(For the suggestion above)

"package-ecosystem" section of Configuration options for dependency updates

• Add a brief sentence, similar to that for vendor mentioning private registries and linking to registries.

Ooh ok

[CBID2]

Hi @CBID2

I'm not seeing an edit / a File changed for this update? (For the suggestion above)

"package-ecosystem" section of Configuration options for dependency updates

• Add a brief sentence, similar to that for vendor mentioning private registries and linking to registries.

Hi @am-stead! :) I made the changes! :)

[am-stead]

👋 @CBID2,
Thanks so much for pushing those new changes. It's looking great!
I've left a couple of final suggestions to bring the changes in line with the issue, and then I think it will be ready to ship! ✨

[CBID2]

Hi @am-stead! :) I made the necessary changes! :)

[am-stead]

👋 @CBID2,

This looks great! ✨

I just pushed a couple of commits to resolve a failing test and align the link text.
But as soon as I see that the tests are all now passing, I'll get it merged! 🚀

Thank you so much for contributing to the docs! 💖

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡