Docs: add guidance for previous-id metadata

[jcogs33]

Proposal for a previous-id tag property to track when alerts are moved to a different query. This is relevant for the current work on migrating the expert services quality queries.

Let me know if this should be a property (e.g. @previous-id java/query-one) instead of a tag. Switched to a property.

[Copilot]

Pull Request Overview

This PR updates the documentation to add guidance on using a new previous-id metadata tag for queries that have been migrated from a different query.

• Introduces a new guideline for queries with alerts that were previously reported on a different query.
• Provides an example demonstrating the intended usage of the previous-id tag.

Comments suppressed due to low confidence (1)

docs/query-metadata-style-guide.md:142

• Consider clarifying whether the previous-id should always be implemented as a tag or if it could alternatively be a property, as suggested in the PR description. Explicitly stating the intended usage here will help maintain consistency.

+Queries with alerts that used to be reported on a different query should have a `previous-id:<previous-query-id>` tag to refer back to the query where the alerts were originally reported. For example, if alerts from `java/query-one` are now reported on `java/query-two`, then the metadata for `java/query-two` should contain: `@tags previous-id:java/query-one`.

Tip: Copilot only keeps its highest confidence comments to reduce noise and keep you focused. Learn more

[jcogs33]

@adityasharad Should I update this Metadata properties table as well?

Proposed update in bea8ce3.