Install all .NET binaries using an installer stage in Dockerfiles

[lbussell]

Describe the Problem

We need to build images internally using private .NET binaries. We'd like for them to have a similar/identical docker history output to images that are published from public .NET binaries. We also don't want any secrets to be leaked through docker history.

Describe the Solution

All .NET binaries should be installed via a separate "installer" stage. We already follow this pattern in some Dockerfiles, so we just need to apply it to the rest of the images. As a bonus, it should simplify the Dockerfile templates a little.

Images

• Linux .NET images - Update Linux .NET images to use an installer stage #6245
• Windows .NET images - Use installer stage for Windows Server Core Dockerfiles #6249
• Appliance images
  • .NET Monitor - nothing to do
  • .NET Aspire Dashboard - nothing to do
  • YARP - nothing to do

Additional Context

Part of https://github.com/dotnet/dotnet-docker-internal/issues/6782. Follow-up to https://github.com/dotnet/dotnet-docker-internal/issues/6844.

[lbussell]

I filed #6251 as clean-up work.

[lbussell]

All current Appliance images are distroless, and as such, already use installer stages to acquire binaries and don't need changes for this issue. They do need to add support for internal builds, so I'll file a follow-up issue for that.