Fix code fence issues in metrics and tracing documentation to prevent over-localization

[Copilot]

This PR fixes code fence issues in the .NET metrics and tracing documentation where type names and other technical terms were being over-localized in non-English versions of the documentation.

Problem

As reported in #43876, technical terms like string, int, Boolean, and instrument type names were being translated/localized when the documentation was viewed in other languages, leading to confusing and incorrect translations. For example:

• In Czech: Boolean was over-localized
• In German: string was over-localized
• In Russian: multiple technical terms were incorrectly translated

Solution

Added code fences (backticks) around all type names in the "Type" column of attribute tables across the metrics documentation files. This prevents these technical terms from being localized while still allowing the descriptive text to be properly translated.

Files Changed

• built-in-metrics-system-net.md - Fixed all type names in attribute tables (string → string, int → int)
• built-in-metrics-runtime.md - Fixed all type names in attribute tables
• built-in-metrics-diagnostics.md - Fixed all type names in attribute tables
• distributed-tracing-builtin-activities.md - Already properly formatted from previous PR

Example Change

Before:

| `dns.question.name` | string | The name being queried. | `www.example.com` | Always |

After:

| `dns.question.name` | `string` | The name being queried. | `www.example.com` | Always |

This ensures that string won't be translated to local language equivalents while still allowing the description "The name being queried" to be properly localized.

Fixes #43876.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

---

Internal previews

📄 File	🔗 Preview link
docs/core/diagnostics/built-in-metrics-diagnostics.md	.NET extensions metrics
docs/core/diagnostics/built-in-metrics-runtime.md	.NET runtime metrics
docs/core/diagnostics/built-in-metrics-system-net.md	System.Net metrics
docs/core/diagnostics/metrics-collection.md	docs/core/diagnostics/metrics-collection

[gewarren]

@copilot Are there any instrument names that should be surrounded with backticks?

[IEvangelist]

For future reference @copilot, if a .NET version is listed, do not change it, as that can alter the meaning. For example, you in some places you changed .NET 8.8.0. to .NET 8.` which is misleading.

[gewarren]

For future reference @copilot, if a .NET version is listed, do not change it, as that can alter the meaning. For example, you in some places you changed .NET 8.8.0. to .NET 8.` which is misleading.

Actually I changed those, but the changes have been superseded by #47584.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.