3.2.0 breaks caching system due to `circleci` lacking the `env` subcommand

## Orb version:

3.2.0 (specifically as of the commits from #131) - can confirm dropping back to 3.1.0 avoids the issue

## What happened:

`circleci local execute name-of-job` results in:

```
Error: unknown command "env" for "circleci"
Run 'circleci --help' for usage.
ERRO[0000] Exit with status 1 due to generic error error="unknown command \"env\" for \"circleci\""
```

stemming from an internal script (the one for linking lockfiles) calling out to `circleci env subst`.

I wasn't able to determine exactly where this ends up running; or rather, why the `circleci` it calls is neither visible in eg `docker run --rm -it cimg/python:3.8` (for any tags, eg behavior is same under `cimg/python:3.13`) nor matching the version in my localhost's environment (which is the latest possible `circleci` and does have `circleci env subst`).

I also haven't progressed to pushing my CI config updates to the server so I'm not sure if this issue occurs outside of `circleci local`.

## Expected behavior:

Expected to actually run my task locally, as happens correctly with orb 3.1.0 and below, usually leading to errors that are actually my fault 😂

## Additional Information:

Not super likely to matter but my execution environment is Arch Linux pinned to a 2024-ish archive repo. my `circleci` CLI version is `0.1.32638+2bfc35c (release)`.

Commencez par le script interne de liaison des lockfiles mentionné dans le rapport et suivez l’endroit où `circleci local execute` appelle `circleci env subst`. Comparez le comportement entre orb 3.2.0 et 3.1.0, puis vérifiez que l’exécution locale signalée se termine après cette commande sans l’erreur de sous-commande inconnue.

Rédigé par le modèle d'indexation à partir du texte de l'issue.