GH4278: Update Spectre.Console to 0.49.1

[devlead]

• fixes Update Spectre.Console to 0.49.1 #4278

[devlead]

It would seem Spectre.Console 0.48.0 has a breaking change with settings like

cake/src/Cake/Commands/DefaultCommandSettings.cs

Lines 55 to 57 in ed61202

	[CommandOption("--version|--ver")]
	[Description("Displays version information.")]
	public bool ShowVersion { get; set; }

This test fails

cake/src/Cake.Tests/Unit/ProgramTests.cs

Lines 101 to 104 in ed61202

	[Theory]
	[InlineData("--version")]
	[InlineData("--ver")]
	public async Task The_Version_Option_Should_Call_Version_Feature(params string[] args)

only the last --ver works.

not investigated the root cause fully.

[devlead]

Found the issue Spectre.Console.Cli no longer allows default commands to have a --version parameter, which Cake relied on to have it's own custom version command.

spectreconsole/spectre.console@131b37f#diff-d38c9fa48d9c39f8eec58957b2333d13943f2cbe1adee26f30325e527a56f600L26-R41

Will see if I can find away around that, can't use the default Spectre version command as it will produce a version string that will break Cake cli contract. Overriding command settings ApplicationVersion and removing cake version feature should probably achieve the same result for end user.

[devlead]

As it's by design breaking change in Spectre.Console.Cli, I just added a workaround to opt-out of this behavior for Cake.Tool.

[devlead]

The breaking --version change was revered in Spectre.Console 0.49.1

[devlead]

Ah would seem remaining arguments has changed in Specre.Console.Cli will investigate, PR still WIP.

[devlead]

@cake-build/cake-team this should be ready for review now.

[patriksvensson]

LGTM 👍