PowerShell tasks applies wrong argument order in Nuke v9

[Baune8D]

Usage Information

NUKE 9.0.4 / .NET 8.0.11 / net8.0 / macOS 15.2

Description

Execute the following target using any v9 version of Nuke:

Target Test => _ => _
    .Executes(() =>
    {
        Pwsh(s => s
            .SetFile("LookAtMe.ps1")
            .EnableNoProfile()
            .EnableNonInteractive());
    });

Nuke generates the following command: /usr/local/bin/pwsh -File LookAtMe.ps1 -NoProfile -NonInteractive

Here -NoProfile and -NonInteractive are sent as arguments to the LookAtMe.ps1 script instead of the pwsh process.

Using the same target with Nuke 8.1.4 generates this: /usr/local/bin/pwsh -NoProfile -NonInteractive -File LookAtMe.ps1

Reproduction Steps

Execute target from description and observe generated command.

Expected Behavior

NoProfile and NonInteractive should be applied before the -File argument.

Actual Behavior

NoProfile and NonInteractive are applied to the -File script as arguments.

Regression?

This was working properly in Nuke 8.1.4

Known Workarounds

None

Could you help with a pull-request?

No