Update Oryx feature to install if a newer version of .NET is present

[seesharprun]

Oryx fails to install if a newer version of .NET is present.

I suspect this is due to a missing --framework argument.

I also took this opportunity to spell out the full name of other dotnet build and dotnet publish arguments to make it easier to debug for the person that comes next.

[seesharprun]

This PR is an attempt to resolve:

• Update universal image to .NET 8 images#855
• [Bug] Oryx tool needs to be built with .NET 7 #760

[seesharprun]

There is still some more work that needs to be done. Even on my local machine, I can't build Oryx from source if I have both .NET 7 and .NET 8 installed.

[seesharprun]

It looks like the feature runs dotnet --version which will always return the latest version of .NET.

Instead it should check dotnet --list-sdks to see if .NET 7 is included in the list.

[seesharprun]

A little more investigating has uncovered that some of the assemblies (Ex: Microsoft.NET.Sdk.Razor/source-generators/Microsoft.NET.Sdk.Razor.SourceGenerators.dll) will always use the latest .NET version if multiple versions are enabled.

I looked around on GitHub and found a couple of example issues where the .NET team says this is intentional behavior. They don't want someone to "freeze" on an old dependency and lock it in for years after moving on to newer versions of .NET.

[seesharprun]

Examples:

• How to avoid the Microsoft.CodeAnalysis.NetAnalyzers.targets warning about newer analyzers available dotnet/docs#27800
• Build failed after upgrade to .Net 8.0 Preview 2.23153.2 and Visual Studio 2022 Professional 17.5.2 dotnet/sdk#31295

[seesharprun]

I have a new PR open on the Oryx repo to see if they are willing to bump their .NET 7-locked dependencies forward so the project can be built on both a .NET 7 and a .NET 7 + 8 environment.

[samruddhikhandale]

Feel free to close this in favor of #825 which should unblock devcontainers/images#855