Remove dnx.ps1

[dsplaisted]

See #51067. The .ps1 script prevents the CLI from correctly processing --. So we'll remove the script, This will regress to the "terminate batch job" behavior described in #49623, but that's better than incorrectly processing command line arguments.

Description

Removes dnx.ps1 helper script.

Customer impact

Fixes processing of -- when calling dnx from PowerShell.
Brings back "Terminate Batch Job" prompt when CTRL+C is pressed, but this is preferrable to incorrectly processing the command line.

Regression

dnx is new in .NET 10. This was a regression from a previous preview release.

Risk

Low

[baronfel]

/ba-g GenerateBundle known issue

[baronfel]

This LGTM but we need to get Tactics approval

[baronfel]

@dotnet/dotnet-docker-admin this PR would remove the dnx.ps1 file due to negative user impacts - it looks like this file is part of the Windows containers - how much work is it to clean it up there?

[lbussell]

@dotnet/dotnet-docker-admin this PR would remove the dnx.ps1 file due to negative user impacts - it looks like this file is part of the Windows containers - how much work is it to clean it up there?

It's easy to remove it. dotnet-docker's PR validation should fail whenever the change flows in, at which point we can just revert the change.

[dotnet-policy-service]

Added needs-breaking-change-doc-created label because this PR has the breaking-change label.

When you commit this breaking change:

1. Create and link to this PR and the issue a matching issue in the dotnet/docs repo using the breaking change documentation template, then remove this needs-breaking-change-doc-created label.
2. Ask a committer to mail the .NET SDK Breaking Change Notification email list.

You can refer to the .NET SDK breaking change guidelines