Use ArtifactsPath

[timcassell]

Fixes #2425
Fixes #2664

We set ArtifactsPath if the dotnet sdk used supports it (v8.0 or higher). Older sdks still use the same build logic as previous, and as far as I could find out, it's the best we can do for those older sdks.
Passing ArtifactsPath also makes MSBuild output publish directory differently by default, so we pass PublishDir also to work for both old and new sdks.

[timcassell]

@adamsitnik Based on your comment #2693 (comment), should we just always use ArtifactsPath and not worry about older sdks here?

[filzrev]

I want to use this PR feature for benchmarks that use multi NuGet versions.

Is it possible to raise priority for review/merge?
And available as nightly build package?

[AndreyAkinshin]

The end of support for .NET SDK 7.0 is May 14, 2024, which is about a year away. I suggest dropping support for .NET SDK 7 and requiring .NET SDK 8 or higher. This change would allow us to use ArtifactsPath everywhere by default, eliminating the need to pass useArtifactsPath repeatedly. Additionally, we should implement a warning for users attempting to run BenchmarkDotNet with older versions of the SDK.

[timcassell]

Updated to your feedback. If we merge #2725, we can update the warning message to tell the user to disable parallel builds (or we could do it automatically).