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

Comienza en LibGit2Sharp/Core/Handles/Libgit2Object.cs alrededor de la línea 88 y, después, sigue el finalizer y las sobrecargas de liberación nativa en LibGit2Sharp/Core/Handles/Objects.cs alrededor de las líneas 502-505. Compara esas rutas de ownership con las directrices de SafeHandle y los informes de runtime enlazados. El trabajo estará terminado cuando las rutas relevantes del ciclo de vida de los handles nativos estén representadas y liberadas de forma segura, sin la condición de carrera del finalizer indicada.