Update the Gee.External.Capstone package

[DrewScoggins]

The Gee.External.Capstone package ships with a native implementation of Capstone, but the last time they pushed a release was 2022. Since then, we require that native binaries be compiled with more security features that are not present on the binary. This means that when we try and use BDN, it breaks on our binary scanning checks.

The Gee.External.Capstone seems to be abandoned, no merges since Jan 2023. A brief search doesn't show any other project that has .Net bindings for the Capstone framework. We could fork that project and put out an updated Nuget with newer native deps, but I am not sure what the maintainers want to do.

@timcassell @AndreyAkinshin @adamsitnik

[timcassell]

I believe we use Capstone for Arm disassembly because Iced only supports x86. If there is another more modern solution we could switch to it would probably be fine. Or if MS wants to own it and we update to whatever MS ships, that'd be cool, too.

[adamsitnik]

The Gee.External.Capstone seems to be abandoned, no merges since Jan 2023.

Let's see if the owner (@9ee1) responds either here or in 9ee1/Capstone.NET#46.

If they are open to contributions, we could just provide the update (9ee1/Capstone.NET#34 (comment) shows what I had to do in the past to contribute arm64 support) and ask them to release a new version.

[MichalPetryka]

I believe we use Capstone for Arm disassembly because Iced only supports x86. If there is another more modern solution we could switch to it would probably be fine. Or if MS wants to own it and we update to whatever MS ships, that'd be cool, too.

BDN should probably switch to the builtin DOTNET_JitDisasm as mentioned in #2062, the only issue is that it can't support Depth this unless it disasms all methods and filters afterwards, which can be huge.