Pack RID-specific tool pointer packages with DotnetToolSettings.xml under tools/any/any

[Copilot]

RID-specific tool packaging currently places the top-level pointer package's DotnetToolSettings.xml under a concrete TFM path. This change makes the pointer package emit the settings file under tools/any/any so the package remains TFM-agnostic while still pointing to the RID-specific payload packages.

• Packaging layout

  • Update Microsoft.NET.PackTool.targets so the top-level RID-specific pointer package writes DotnetToolSettings.xml to tools/any/any/.
  • Leave implementation packages unchanged; they still use their existing TFM/RID-specific layout.

• Pointer package behavior

  • Apply the any TFM path only when packing the RID-specific top-level package that contains metadata but no implementation files.
  • Preserve the existing settings generation and RID declarations inside the XML.

• Coverage

  • Extend tool packaging end-to-end assertions to verify the pointer package contains exactly one DotnetToolSettings.xml and that its path is tools/any/any/DotnetToolSettings.xml.
  • Cover both standard RID-specific packages and the variant that also includes an any RID payload.

<!-- top-level pointer package -->
tools/any/any/DotnetToolSettings.xml

<!-- RID-specific implementation package -->
tools/net11.0/linux-x64/...

[baronfel]

When we merge this we should backport to 10.0.4xx as well.

[Copilot]

Pull request overview

This PR updates the RID-specific pointer tool package layout so that DotnetToolSettings.xml is emitted under tools/any/any/, keeping the pointer package TFM-agnostic while still referencing RID-specific implementation packages.

Changes:

• Adjust Microsoft.NET.PackTool.targets to place the pointer package’s DotnetToolSettings.xml under tools/any/any/ (while keeping implementation packages’ existing TFM/RID layout).
• Extend end-to-end tool packaging assertions to validate the pointer package contains exactly one DotnetToolSettings.xml and that it lives at tools/any/any/DotnetToolSettings.xml.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
test/Microsoft.DotNet.PackageInstall.Tests/EndToEndToolTests.cs	Adds assertions to verify the pointer package has a single DotnetToolSettings.xml at tools/any/any/.
src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.PackTool.targets	Updates packing logic to emit DotnetToolSettings.xml to a TFM-agnostic tools/any/any/ path for RID-specific pointer packages.

[dsplaisted]

I think multi-targeted tool packages can contain more than one tool settings file. But this is probably fine for the scenarios we're testing.