Feature: Add extensibility to the DotnetCliCommand

[dmitriyse]

It would be beneficial if all methods of the DotnetCliCommand were virtual.

It's impossible to customize the build/restore behaviour of the CsProjCoreToolchain.

Motivation:
For large project, it's beneficial to use all CPU cores for compilation

The disabled parallel build:

/p:BuildInParallel=false /m:1

can be replaced with

--nodeReuse:false

[timcassell]

I imagine we could just branch off of the sdk version, using --nodeReuse:false for the sdks that support it, and using /p:BuildInParallel=false /m:1 for older sdks.

cc @adamsitnik Who added those arguments.

[adamsitnik]

I have added this many years ago, but I was lucky enough to add a comment for future myself:

BenchmarkDotNet/src/BenchmarkDotNet/Toolchains/DotNetCli/DotNetCliCommand.cs

Lines 218 to 219 in 804482d

	// we use these settings to make sure that MSBuild does the job and simply quits without spawning any long living processes
	// we want to avoid "file in use" and "zombie processes" issues

If .NET 8+ SDK (I don't believe we should add any complexity for recognizing older, unsupported SDKs) does not start any long-living processes with --nodeReuse:false I am supportive of replacing /p:BuildInParallel=false /m:1 with this argument 👍