Add macOS Arm64 support to the CLI tool

[rjrjensen]

Is your feature request related to a problem? Please describe.

I am trying to run the libman CLI tool on my Mac mini M2 Pro after installing the recommended Arm64 versions of the .NET SDK, but it fails and says that it can't find a .NET Runtime.

Describe the solution you'd like

Correct me if I'm wrong, but I think the problem could be solved if osx-arm64 was added to the PackAsToolShimRuntimeIdentifiers tag in

LibraryManager/src/libman/libman.csproj

Line 8 in b0570cd

<PackAsToolShimRuntimeIdentifiers>win-x64;win-x86;osx-x64</PackAsToolShimRuntimeIdentifiers>

I saw a lot of macOS RIDs here and none of them were specifically "osx-arm64", but they do have "osx.13-arm64", so you'd think they'd have a non-version-specific one.

Describe alternatives you've considered

I solved the issue momentarily by installing the x64 version of the Runtime, but I read that running that version uses an Intel emulator and I'm wondering if there's overhead there.

[dvtkrlbs]

+1 for this. I tried forking the project and adding osx-arm64. However it started complaining about not being able to find the app host for osx-arm64 even though my dotnet tool is arm64 version. I could try to add build configuration for this with some guidance.

[AustinWise]

This will also requiring update this project from targeting .NET Core 2.1 to at least .NET 5. That is the first version of .NET that support ARM64 macOS.

[dvtkrlbs]

That should be ok IMHO since .NET Core 2.1 has been out of support since August of 2021. .NET Core 5 is also out of support as a lowest common denominator I think it is a good version to bump to.

[jimmylewis]

@phil-allen-msft can someone look at validating support for osx-arm64 now that the CLI tool has been updated to .NET 8?