Enhance Readability and Structure of Docs Metadata YAML

[NirajDN]

Why:

This PR improves the readability, maintainability, and structure of the GitHub Docs metadata YAML configuration. It removes redundant entries, consolidates related keys, and optimizes formatting for better clarity and easier future updates.

Closes: N/A (no existing issue, but improves code quality and maintainability)

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

• Removed duplicated or unnecessary keys to reduce clutter.
• Standardized formatting and indentation for consistency.
• Grouped related settings logically for better structure.
• Improved comments and placeholder text for clarity.
• Ensured all keys follow consistent naming conventions.

These changes do not affect functionality but enhance the quality of the codebase and make it easier for contributors to maintain and extend the configuration.

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.

[Copilot]

Pull Request Overview

This PR improves the readability and maintainability of the GitHub Docs YAML configuration file by restructuring the content with better formatting, consistent indentation, and logical grouping. The changes focus on enhancing code quality without affecting functionality.

Key changes include:

• Converted single-line strings to multi-line YAML format using > and >- operators for better readability
• Added consistent spacing and section breaks between major configuration groups
• Standardized quote usage around string values containing special characters

[Copilot]

The line appears to be incomplete. The allows key is cut off and missing its value, which will cause YAML parsing errors.

Suggested change

	allows
	allows: []

[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.

This pull request contains code changes, so we will not generate a table of review links.

🤖 This comment is automatically generated.