Overhaul documentation issue section in "How to report a problem with the Microsoft C++ toolset or documentation"

[Rageking8]

Remove mentions of the now disabled GitHub issues, guide users to the feedback buttons on the page, and provide information on the new feedback system rolled out in 2024.

[prmerger-automator]

@Rageking8 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit 65b3645:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/overview/how-to-report-a-problem-with-the-visual-cpp-toolset.md	✅Succeeded

For more details, please refer to the build report.

[v-dirichards]

@TylerMSFT

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[learn-build-service-prod]

Learn Build status updates of commit 7f80e59:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/overview/how-to-report-a-problem-with-the-visual-cpp-toolset.md	✅Succeeded

For more details, please refer to the build report.

[ktoliver]

Merge conflict resolved.

@TylerMSFT - Would you review this proposed update to your article and enter #sign-off in a comment if it's ready to merge?

Thanks!

[TylerMSFT]

#sign-off

[Copilot]

Pull Request Overview

This PR updates the documentation to reflect changes in how C++ documentation issues are reported. The update removes outdated information about the GitHub issues workflow and replaces it with current guidance about the new Microsoft Learn feedback system introduced in 2024.

Key changes:

• Removed outdated GitHub issues workflow description
• Added reference to the new 2024 feedback system with a link to the announcement
• Streamlined the content to focus on current feedback mechanisms and open-source contribution options