feat: Add disassembler support for macos

[filzrev]

This PR intended to add DisassemblyDiagnoser supports for macos.

Currently DisassemblyDiagnoser is not supported on macos.
This limitation appears to be coming from the ClrMD library.
And It seems to be resolved in the latest version.

[timcassell]

You tested it? The issues on ClrMD are still open. microsoft/clrmd#1034 microsoft/clrmd#1230

[filzrev]

I've not noticed issues listed above. I confirmed only https://github.com/microsoft/clrmd/issues/888

And I'm only confirmed unit tests passed on CI. (Because I'm not have mac)
If it's still not works on macos. Please close this PR.

[filzrev]

Note: This changes affects windows-11-arm tests also.

[filzrev]

DisassemblyDiagnoserTests seems successfully passed on both macos(x64/arm64)

It would be helpful if someone could confirm DisassemblyDiagnoser's behaviors with an actual mac device.
In particular, it would be helpful to verify that the following code paths are working on macOS.

BenchmarkDotNet/src/BenchmarkDotNet/Disassemblers/ClrMdV3Disassembler.cs

Lines 48 to 50 in ed5316b

	using (var dataTarget = DataTarget.AttachToProcess(
	settings.ProcessId,
	suspend: false))

[filzrev]

It seems ShouldUseSameArchitectureDisassembler method also need to be modified.

BenchmarkDotNet/src/BenchmarkDotNet/Disassemblers/DisassemblyDiagnoser.cs

Lines 149 to 165 in f8390f8

	private static bool ShouldUseSameArchitectureDisassembler(BenchmarkCase benchmarkCase, DiagnoserActionParameters parameters)
	{
	if (ShouldUseClrMdDisassembler(benchmarkCase))
	{
	if (OsDetector.IsWindows())
	{
	return WindowsDisassembler.GetDisassemblerArchitecture(parameters.Process, benchmarkCase.Job.Environment.Platform)
	== RuntimeInformation.GetCurrentPlatform();
	}
	// on Unix currently host process architecture is always the same as benchmark process architecture
	// (no official x86 support)
	return true;
	}
	return false;
	}

Because macos (on ARM64) support running x86/x64 binary by using Rosetta2.
Rosetta2 is optional feature and it will be not supported in future releases.

So when specified binary has different architecture on macos.
It should be skipped same as previous behavior.