Using yarn instead of npm to install function's dependencies

In my project, we use yarn and yarn workspaces to manage all dependencies, and I noticed that every time functions are deployed or mocked, the package-lock.json file is generated. Is there a way to set yarn as the default tool or ideally disable installing dependencies step?

The issue does not name files, tests, or entry points. Start by tracing dependency installation during function deployment and mocking, then verify whether the completed behavior supports Yarn or skips installation without generating package-lock.json.

Written by the indexing model from the issue text.