Concurrent first-run CLI processes race on release extraction: parallel CI deploys fail with "Cannot find package"

Issue description

We have a relatively rare issue that I'm trying to debug. We use Turobrepo to manage our monorepo, which consists of roughly 15 Serverless services. To date, during a deployment, all of the services have depended on one service before executing the remaining services in parallel, thus ensuring the Serverless instance can be instantiated correctly. However, we've started introducing caching to speed up our CI/CD which means services are now deploying in parallel from the get go. This results in the following error:

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'esbuild' imported from /home/runner/.serverless/releases/4.4.14/package/dist/sf-core.js
    at packageResolve (node:internal/modules/esm/resolve:854:9)
    at moduleResolve (node:internal/modules/esm/resolve:927:18)
    at defaultResolve (node:internal/modules/esm/resolve:1157:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39)
    at link (node:internal/modules/esm/module_job:86:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}

This only occurs when we try to deploy multiple services in parallel from the get go. I've tried to instantiate the CLI via a --version command but that has no impact:

      - name: Initiate Serverless environment
        run: yarn sls --version

      - name: Turbo serverless deploy
        run: yarn deploy:ci

We're pinned to version 4.4.14 of the framework and running node 20.14.0. I'll try and put a repeatable example together.

Context

This impacts multiple services. Can provide if necessary.