feat: avoid dependency on git binary

[beeb]

Component

Forge

Describe the feature you would like

Forge uses the git CLI for many operations, so does Soldeer (which is used in the forge soldeer subcommand).

Would it be acceptable to start rewriting the operations that depend on git to use the gix library?

This would avoid potential inconsistencies when it comes to the git version installed by the user, and would avoid the overhead of spawning a new process. Also, it reduces the potential for errors when parsing the output of the git command.

I could start by rewriting Soldeer to use gix as a proof-of-concept, if the additional dependency is acceptable.

Additional context

No response

[zerosnacks]

I think this makes sense but would be good if it is done following an exploration in Soldeer so we can better evaluate the impact and usefulness. Any objections @onbjerg / @DaniPopes / @grandizzy? It is also unlikely any of us have the bandwidth / can prioritize this.

[mablr]

Closing as not planned. I explored this in #14452. While gix could replace some read-only operations, Forge would still need the Git binary for cloning, checkout, index mutation, and extensive submodule management.

A partial migration would add a second Git implementation without removing the dependency or providing enough benefit to justify the added complexity. We can reconsider if gix eventually supports the complete workflow.

[beeb]

Came to the same conclusion while investigating for Soldeer :)