[v11.0.x] Angular deprecation: Prefer local "angularDetected" value to the remote one

[xnyo]

Backport c033a15 from #85571

---

What is this feature?

Ensures that, in the catalog, Grafana prefers the local angularDetected value (provided by the Grafana backend, so the value for the plugin that's actually installed) to the remote one (provided by GCOM, so the value for the latest version published in the catalog).

This fixes an issue where the angular badge and warning are displayed in the catalog pages when testing an unpublished plugin that has stopped using Angular, but whose latest published version in GCOM is marked as angularDetected = true.

Before this PR, in such scenario Grafana used to prefer the value in GCOM (angularDetected = true) to the one for the new unpublished version (angularDetected = false).

This new behaviour introduced in the PR is more clear, especially for plugin developers who are testing a WIP/unpublished plugin update that migrated the plugin from Angular to React.

Why do we need this feature?

Solves confusion for plugin developers migrating Angular plugins to React.

Who is this feature for?

Plugin developers, but all Grafana users in general as well, because this behaviour makes more sense.

Which issue(s) does this PR fix?:

Fixes #

Special notes for your reviewer:

Please check that:

• It works as expected from a user's perspective.
• If this is a pre-GA feature, it is behind a feature toggle.
• The docs are updated, and if this is a notable improvement, it's added to our What's New doc.