[BUG] Version manager sets different version in different folders in Docker

🐛 Bug Report:

Describe the bug

I am running the CLI as part of a Bitbucket pipeline in a Docker container. The v7.2.0 update broke our pipeline because of an Axios version update. It's easy enough to set the openapi-generator version back to v7.1.0 using openapi-generator-cli version-manager set 7.1.0. I put this line in my Dockerfile.

However, I saw that v7.2.0 was still being used. Debugging it locally by building the Docker container and attaching to it, I see at the root level, openapi-generator-cli version is set to 7.1.0, but changing to a copied-in folder where the pipeline work is done, the version is 7.2.0.

Steps to Reproduce

Steps to reproduce the behavior:

1. Build a Docker container where openapi-generator-cli is installed via npm, and the openapi-generator version is set to a version other than the latest (7.2.0 at time of writing).
2. Attach to Docker container and check version of openapi-generator the CLI is using.
3. Switch directories
4. Check the version of openapi-generator being used

Expected behavior

The openapi-generator version should be the same, regardless of directory

Operation System (please complete the following information):

• Docker image from node:16.20.1-alpine

Package System (please complete the following information):

• NPM v8.19.4
• openapi-generator-cli v2.8.0

Additional context

The following commands are in my Docker file to install and set the CLI

RUN npm install -g @openapitools/openapi-generator-cli@2.8.0
RUN openapi-generator-cli version-manager set 7.1.0