Adding new feature under TSG v4 release

[shshakya]

Summary

Updates the High CPU Usage troubleshooting workbook for PostgreSQL Flexible Server with the following improvements:

What changed:

• Consolidated the header and diagnostic steps into a single markdown block, replacing the separate header + steps table + parameter label sections
• Replaced 7 separate conditional error message blocks with a single CombinedErrorMessages KQL-driven parameter that dynamically renders a consolidated error table
• Added new parameters for replica query text checks: isQueryTextSendToLogAnalytics, EmitQueryTextCheck, isEmitQueryTextEnabled
• Switched Transactions tab from KQL-based xact_total queries to native MetricsItem/2.0 charts using the GA tps metric
• Updated metric namespaces from database (Preview) to Database (GA)
• Fixed IsServerPrimaryAPI query to normalize replication role values with regex matching
• Removed unused parameters: AzureDiagAPIMetrics, IsAllMetricsSentToLogAnalytics, IsMetricDataExists
• Changed resourceType from microsoft.resourcegraph/resources to microsoft.operationalinsights/workspaces

Why:

• Improve readability and reduce maintenance overhead (one error block vs seven)
• Support replica-specific diagnostics (query text availability on replicas)
• Use GA metrics instead of preview
• Better error guidance with actionable table format

Screenshots

• If you added a template to a gallery, show a screenshot of it in the gallery view (which verifies its shows up where you expected).

  It is also good to show a screenshot of template content, so people can see what you expect it to look like, compared to what they see when they might run it themselves.

Validation

• Validate your changes using one or more of the testing methods.

  Make sure you've tested your template content. Fixing things while in PR is trivial. Hotfixing it later is very expensive; at the current time at least 3 teams are involved in a hotfix!

Checklist

• If you are adding a new template, gallery, or folder, add your team and folder/file(s) to the CODEOWNERS file at the root of the repo. CODEOWNERS entries should be teams, not individuals.
  When done correctly, this means that from then on your team does reviews of your things, not the workbooks team.
• Ensure all steps in your template have meaningful names.
• Ensure all parameters and grid columns have display names set so they can be localized.