step-runner v0.17.0 Fails to Clone Steps
## Problem
After the release of v0.17.0, our pipelines using steps hosted in another repository on same GitLab instance started failing with the following message (details redacted).
```
Error: failed to run steps: step "step00": failed to load: fetching git step: storing SHA for ref "feature/test00": open /tmp/step-runner-cache/selfmanaged.gitlab.company.org/group/project/.refs/feature/test00.sha: no such file or directory
```
Reverting to v0.16.0 resolves the issue.
Note that we build our own image and execute the job using that. Our image acquires `step-runner` from `registry.gitlab.com/gitlab-org/step-runner` with the following Dockerfile directive.
```Dockerfile
COPY --from=registry.gitlab.com/gitlab-org/step-runner:latest /step-runner /usr/bin/
```
## Failure Behavior
Job fails at first attempt to execute a step with the following output.
```
Executing "step_script" stage of the job script 00:01
$ step-runner ci
***** WARNING *****
As of GitLab Runner 17.11, the legacy step-runner image registry.gitlab.com/gitlab-org/step-runner:v0 is replaced by the image defined by the job.
The legacy step-runner image will be supported until GitLab 18.0.
See https://docs.gitlab.com/ci/steps/ for information on how to configure CI/CD Steps.
***** END WARNING *****
Error: failed to run steps: step "step00": failed to load: fetching git step: storing SHA for ref "feature/test00": open /tmp/step-runner-cache/selfmanaged.gitlab.company.org/group/project/.refs/feature/test00.sha: no such file or directory
```
## Steps to Reproduce
Minimal steps to reproduce TBD, if needed. Some clues, though, are that we have one repository that contains a template and steps and several other repositories that utilize it. The template is pulled into the desired pipelines as a component. The template then expands the jobs that reference the steps. The steps are referenced via HTTP.
e.g. _not a full example, just a minimal snippet_
```
Run Stuff:
image:
name: custom-step-runner-image
run:
- name: step00
step: https://oauth2:${{job.CI_PULL_TOKEN}}@${{job.CI_SERVER_FQDN}}/group/project/-/step00@feature/test00
```
issue