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

Comece em LibGit2Sharp/Core/Handles/Libgit2Object.cs por volta da linha 88 e, em seguida, acompanhe o finalizer e as sobrecargas de liberação nativa em LibGit2Sharp/Core/Handles/Objects.cs por volta das linhas 502-505. Compare esses caminhos de ownership com as orientações de SafeHandle e os relatórios de runtime vinculados. O trabalho estará concluído quando os caminhos relevantes do ciclo de vida dos handles nativos estiverem representados e liberados com segurança, sem a condição de corrida do finalizer relatada.