Consider using SafeHandle in Libgit2Object instead of void*

We've had a couple of bug reports against dotnet/runtime with rarely-reproduceable crashes coming from libgit2sharp. We believe that one possible reason could be an interop anti-pattern in Libgit2Object - void*/IntPtr representation of a native handle that can be freed in finalizer. E.g. in this case the finalizer in Libgit2Object may end up calling native free here (and other overloads).

The reason why it's called an anti-pattern can be explained by a short repro in this issue: https://github.com/dotnet/runtime/issues/103522 and a general solution is to use SafeHandle for such handles. Also, see https://learn.microsoft.com/en-us/dotnet/standard/native-interop/best-practices

Reproduction steps

Expected behavior

Actual behavior

Version of LibGit2Sharp (release number or SHA1)

Operating system(s) tested; .NET runtime tested

从 LibGit2Sharp/Core/Handles/Libgit2Object.cs 第 88 行附近开始，然后跟踪 LibGit2Sharp/Core/Handles/Objects.cs 第 502-505 行附近的 finalizer 和 native-free overloads。将这些 ownership 路径与 SafeHandle 指南及链接的 runtime 报告进行比较。完成的标准是：相关的 native handle 生命周期路径得到安全表示并被释放，且不会出现报告中的 finalizer race。