Fix shared-components storybook:update script (#32486)

It was failing due to being unable to access pnpm-workspace.yaml so change the docker context to the root of the monorepo

Also disable pnpm-link script in the docker env and node-linking for storybook tests

Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>

packages/shared-components/package.json

@@ -40,7 +40,7 @@
         "i18n:lint": "matrix-i18n-lint && prettier --log-level=silent --write src/i18n/strings/ --ignore-path /dev/null",
         "test:unit": "vitest --project=unit",
         "test:storybook": "pnpm build:doc && vitest --project=storybook",
-        "test:storybook:update": "playwright-screenshots --entrypoint /work/scripts/storybook-screenshot-update.sh --with-node-modules",
+        "test:storybook:update": "cd ../.. && playwright-screenshots --entrypoint /work/packages/shared-components/scripts/storybook-screenshot-update.sh --with-node-modules --no-link-modules",
         "build": "vite build",
         "prepack": "pnpm run build",
         "storybook": "storybook dev -p 6007",

packages/shared-components/scripts/storybook-screenshot-update.sh

@@ -13,7 +13,7 @@ set -e
 # because we have which must be built for the right architecture (and some environments use a VM
 # to run docker containers, meaning that things inside a container use a different architecture than
 # those on the host).
-pnpm install
+pnpm install --frozen-lockfile
 
 # Now run the screenshot update, we set CI=1 to inform vis to update the real baselines
-CI=1 /work/node_modules/.bin/vitest --run --update --project=storybook "$@"
+CI=1 pnpm --dir packages/shared-components test:storybook --run --update