fix(core): use binjumper to work-around 'Terminate batch job' prompts on Windows

[merceyz]

What's the problem this PR addresses?

Due to the use of cmd jumper-files to spawn binaries, terminating scripts on Windows is horrendously annoying since CMD provides no way to disable the Terminate batch job (Y/N) prompt

Fixes #1592

How did you fix it?

Create the jumper files using https://github.com/merceyz/binjumper to avoid the prompts

Checklist

• I have read the Contributing Guide.
• I have set the packages that need to be released for my changes to be effective.
• I have verified that all automated PR checks pass.

[arcanis]

since CMD provides no way to disable the Terminate batch job (Y/N) prompt

Would creating a Powershell script instead of CMD work? The builtin binaries approach is a bit magical, I'm slightly worry it would open us to weird differences between spawning a binary from a script versus from a shellscript spawned by a script 🤔

[merceyz]

Would creating a Powershell script instead of CMD work?

While Powershell doesn't create the prompt it seems cross-spawn doesn't know how to handle them, I added .ps1 to the PATHEXT but it just opens the file in Visual Studio.

The builtin binaries approach is a bit magical, I'm slightly worry it would open us to weird differences between spawning a binary from a script versus from a shellscript spawned by a script

The difference would be the prompt, otherwise it shouldn't be noticable 🤔

[arcanis]

Related: microsoft/terminal#217

[cowboyd]

Can we backport this to 1.x? I'd be happy to give it a shot.

[arcanis]

@cowboyd 1.x is in feature freeze, only security issues will be addressed. I suggest you take a look at the migration guide if you need features introduced in the 2.x.