Bazel will always pick a version that is with in compatibilty level range.

Uses a read-only SSH deployement key for testing SSH fetching.

Provides a common way to parse an incoming `git` remote specification.

A `remote.Flag` has a `Auth` method to retrieve the `go-git` authentication
to use.

Provides a way to determine the `go-git` authentication to use
with a certain remote. At the moment only `ssh-agent` is supported.

Introduces an circular dependency. We want our testing
to work in an isolated fashion.

To effectively test `bazel-git` with `rules_git` a repository context
time label to a built `bazel-git` needs to be provided.

The `test/build` repository provides a repository context time build
of the project to retrieve a `bazel-git` that can be used in the
`git_fetch` rules in `MODULE.bazel`.

The downside is that an isolated output base must be used to prevent
deadlock when running the build. Duplicated downloads of dependencies
will occur.

The upside is that `bazel-git` is tested in the same way that the
primary downstream ruleset uses the binary.

Bumps to `rules_go@0.48.0`, `gazelle@0.37.0` and `circl@1.3.8`
which all have the support for understanding `purego` build tag.

This allows us to build fully static `bazel-git` binaries.