Fix and test more dotnet file precedence cases

[jjonescz]

Follow up on #49485.

[Copilot]

Pull Request Overview

This PR enhances the dotnet command precedence handling by introducing additional test cases and refactoring key command resolution logic.

• Added tests to ensure proper precedence between built-in, file-based, and NuGet tool invocations.
• Refactored Program.cs to extract file-based app resolution and built-in command invocation into dedicated helper methods.
• Updated CommandFactoryUsingResolver.cs to consistently use a CreateOrThrow method for command creation.

Reviewed Changes

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

File	Description
test/dotnet.Tests/CommandTests/Run/RunFileTests.cs	Adds tests for file-based app precedence cases and NuGet tool scenarios
src/Cli/dotnet/Program.cs	Refactors command invocation logic by extracting helper methods
src/Cli/dotnet/CommandFactory/CommandFactoryUsingResolver.cs	Adjusts command creation using a new CreateOrThrow method

Comments suppressed due to low confidence (1)

src/Cli/dotnet/Program.cs:285

• [nitpick] Consider adding XML documentation comments for the new helper methods 'TryRunFileBasedApp' and 'InvokeBuiltInCommand' to provide clarity on their usage and behavior.

        static int? TryRunFileBasedApp(ParseResult parseResult)

[baronfel]

Nice! Thanks for also taking care of the dotnet-<tool> invocation pattern while you were here!