docs: Document .NET 8 self-contained deployment default change and add troubleshooting

[Copilot]

In .NET 8, specifying -r <RID> no longer implies --self-contained — apps now publish framework-dependent by default even with a RID. This silent behavioral change from .NET 7 has caused widespread confusion (16k-view SO question).

Changes to docs/core/deploying/index.md

• Breaking change callout — Added [!IMPORTANT] alert at the top of the Self-contained deployment section, explicitly stating that -r <RID> alone no longer produces a self-contained app in .NET 8+:

  # .NET 7 behavior (implicit self-contained)
  dotnet publish -r win-x64
  
  # .NET 8+ required form
  dotnet publish -r win-x64 --self-contained

• Troubleshooting section — Added ## Troubleshoot self-contained deployment before ## See also with:

  • App prompts for .NET runtime installation — root cause explanation + fix for both CLI and Visual Studio
  • Verify that publish output is self-contained — tells readers to check for coreclr.dll / libcoreclr.so / libcoreclr.dylib in the publish folder; includes project-file fix via <SelfContained>true</SelfContained>

• See also — Added link to the Runtime-specific apps no longer self-contained breaking change article

---

Internal previews

📄 File	🔗 Preview link
docs/core/deploying/index.md	.NET application publishing overview

[Copilot]

Pull request overview

This PR updates the .NET deployment documentation to highlight the .NET 8 behavioral change where specifying a RID (-r <RID>) no longer implies a self-contained publish, and it adds an additional cross-link to the related breaking change article.

Changes:

• Added an [!IMPORTANT] callout in the Self-contained deployment section describing the .NET 8 breaking change and linking to the breaking change article.
• Added a See also link to the “Runtime-specific apps no longer self-contained” breaking change article.

[gewarren]

Closing per @adegeo. This update isn't necessary.