Update PSReadLine about doc for predictive intellisense and dynamic help

[daxian-dbw]

PR Summary

Update PSReadLine about doc for predictive intellisense and dynamic help.
The dynamic help content is moved to the Miscellaneous functions section because they belong to that group.
Prediction functions were added but not added to the about-* doc.

PR Context

Select the area of the Table of Contents containing the documents being changed.

Conceptual content

• Overview and Install
• Learning PowerShell
  • PowerShell 101
  • Deep dives
  • Remoting
• Release notes (What's New)
• Windows PowerShell
  • WMF, ISE, release notes, etc.
• DSC articles
• Community resources
• Sample scripts
• Gallery articles
• Scripting and development
  • Legacy SDK

Cmdlet reference & about_ topics

• Preview content
• Version 7.1 content
• Version 7.0 content
• Version 5.1 content

PR Checklist

• I have read the contributors guide and followed the style and process guidelines
• PR has a meaningful title
• PR is targeted at the staging branch
• All relevant versions updated
• Includes content related to issues and PRs - see Closing issues using keywords.
• This PR is ready to merge and is not Work in Progress
  • If the PR is work in progress, please add the prefix WIP: or [WIP] to the beginning of the
    title and remove the prefix when the PR is ready.

[opbld32]

Docs Build status updates of commit 034c3c5:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
	❌Error		Details
	❌Error		Details

• [Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://SiteHelp and include the error report for our team to troubleshoot
• Line 0, Column 0: [Warning-validation-incomplete] Failed to get the validation ruleset and validation was not completed. This happens when there's an issue with the service and continuing to retry the call could cause build delays. You might have content issues that were not reported. To retry validation, close and re-open your PR, or rebuild your branch via Docs Portal (requires admin permissions). If you need admin help or if you continue to see this message, file an issue via https://SiteHelp.

• [Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://SiteHelp and include the error report for our team to troubleshoot
• Line 0, Column 0: [Warning-validation-incomplete] Failed to get the validation ruleset and validation was not completed. This happens when there's an issue with the service and continuing to retry the call could cause build delays. You might have content issues that were not reported. To retry validation, close and re-open your PR, or rebuild your branch via Docs Portal (requires admin permissions). If you need admin help or if you continue to see this message, file an issue via https://SiteHelp.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[sdwheeler]

Retrigger build

[opbld31]

Docs Build status updates of commit 034c3c5:

✅ Validation status: passed

File	Status	Preview URL	Details
reference/7.2/PSReadLine/About/about_PSReadLine.md	✅Succeeded	View (powershell-7.2)

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel