grafana: Update grafana datasources

[mauriciovasquezbernal]

Align datasources with docs in https://grafana.com/docs/grafana/latest/datasources/ and the ones I can see in my Managed Grafana workspace:

[prmerger-automator]

@mauriciovasquezbernal : 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 32a2c81:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/managed-grafana/how-to-data-source-plugins-managed-identity.md	✅Succeeded

For more details, please refer to the build report.

[v-dirichards]

Hi @mauriciovasquezbernal - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!

---

@maud-lv

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

[Copilot]

Pull request overview

This PR updates the Grafana datasources table to align with the latest official documentation and the datasources available in Azure Managed Grafana workspaces. The changes add three new datasources (Parca and Pyroscope) and remove a duplicate Loki entry to match the current state of supported plugins.

• Added Parca and Pyroscope datasources to the supported list
• Removed duplicate Loki entry that appeared twice in the table

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[learn-build-service-prod]

Learn Build status updates of commit d367e1a:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/managed-grafana/how-to-data-source-plugins-managed-identity.md	✅Succeeded

For more details, please refer to the build report.

[mauriciovasquezbernal]

Hi @mauriciovasquezbernal - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!

Thanks for the heads up. I didn't know about that repo.