chore(omz-pnpm-plugin): default to v1.1.0, a mirror of upstream (#8)

Upstream ntnyq/omz-plugin-pnpm merged the PNPM_HOME fix (rewritten, with
tests; the plugin no longer calls pnpm on shell start). Upstream publishes
no tags, so the itplusx fork now serves as tag source: v1.1.0 points at
upstream main a5c3b08. Bump the feature to 1.0.1 with that default ref.

feat: own PNPM_HOME in shared-pnpm-store and add omz-pnpm-plugin feat…

…ure (#6)

* feat: own PNPM_HOME in shared-pnpm-store and add omz-pnpm-plugin feature

pnpm downloads the version pinned in a project's `packageManager` into
"$PNPM_HOME/package-manager-store". With PNPM_HOME unset that is a per
container copy under ~/.local/share/pnpm; with PNPM_HOME set but empty
(which ntnyq/omz-plugin-pnpm does when `pnpm -g bin` fails) it ends up in
the project root as `global/` and `package-manager-store/`.

shared-pnpm-store 1.1.0
- set PNPM_HOME=/usr/local/share/pnpm at the image level
- pin the global bin dir to $PNPM_HOME/bin (identical layout on pnpm 10-12)
  and put it on PATH, so `pnpm -g bin` and `pnpm add -g` work
- share $PNPM_HOME/package-manager-store via a second named volume
- create/chown the PNPM_HOME tree in install.sh and oncreate.sh
- tests: assert the new env and mount, add a `version_switch` scenario
  that reproduces the bug with a mismatching `packageManager`

omz-pnpm-plugin 1.0.0
- installs the itplusx fork of omz-plugin-pnpm, which respects a pre-set
  PNPM_HOME and never exports an empty one, into the remote user's
  oh-my-zsh custom plugins and activates it in ~/.zshrc
- vendored system-wide at build time, copied on container create so it
  also works when oh-my-zsh is installed by a later feature
- tests: bare image no-op, common-utils zsh, nils-geistmann zsh,
  activate=false; assert PNPM_HOME survives an interactive zsh

* test(omz-pnpm-plugin): handle base images that ship oh-my-zsh

The autogenerated test assumed no oh-my-zsh on the image, which is wrong
for mcr.microsoft.com/devcontainers/base:ubuntu. Assert the plugin is
installed and activated when oh-my-zsh is present, and the no-op otherwise.

feat: own PNPM_HOME in shared-pnpm-store and add omz-pnpm-plugin feat…

…ure (#6)

* feat: own PNPM_HOME in shared-pnpm-store and add omz-pnpm-plugin feature

pnpm downloads the version pinned in a project's `packageManager` into
"$PNPM_HOME/package-manager-store". With PNPM_HOME unset that is a per
container copy under ~/.local/share/pnpm; with PNPM_HOME set but empty
(which ntnyq/omz-plugin-pnpm does when `pnpm -g bin` fails) it ends up in
the project root as `global/` and `package-manager-store/`.

shared-pnpm-store 1.1.0
- set PNPM_HOME=/usr/local/share/pnpm at the image level
- pin the global bin dir to $PNPM_HOME/bin (identical layout on pnpm 10-12)
  and put it on PATH, so `pnpm -g bin` and `pnpm add -g` work
- share $PNPM_HOME/package-manager-store via a second named volume
- create/chown the PNPM_HOME tree in install.sh and oncreate.sh
- tests: assert the new env and mount, add a `version_switch` scenario
  that reproduces the bug with a mismatching `packageManager`

omz-pnpm-plugin 1.0.0
- installs the itplusx fork of omz-plugin-pnpm, which respects a pre-set
  PNPM_HOME and never exports an empty one, into the remote user's
  oh-my-zsh custom plugins and activates it in ~/.zshrc
- vendored system-wide at build time, copied on container create so it
  also works when oh-my-zsh is installed by a later feature
- tests: bare image no-op, common-utils zsh, nils-geistmann zsh,
  activate=false; assert PNPM_HOME survives an interactive zsh

* test(omz-pnpm-plugin): handle base images that ship oh-my-zsh

The autogenerated test assumed no oh-my-zsh on the image, which is wrong
for mcr.microsoft.com/devcontainers/base:ubuntu. Assert the plugin is
installed and activated when oh-my-zsh is present, and the no-op otherwise.

chore(shared-pnpm-store): bump version to 1.0.1

feat(shared-pnpm-store): add shared pnpm store devcontainer feature

Caches the pnpm content-addressable store in a host-wide Docker named
volume shared across devcontainers, pointing pnpm at it via containerEnv
(no pnpm invocation). install.sh prepares the mount point; oncreate.sh
re-asserts ownership for the remote user on every container create.

Includes README/NOTES and the devcontainer feature test suite
(autogenerated checks plus with_node, pnpm_from_feature, node_v2,
zsh_shell, fish_shell, and root_user scenarios), and lists the feature
in the repo README.

ci: add shared-pnpm-store to test matrix

shared-pnpm-store had no CI coverage. Add it to the autogenerated and
scenarios matrices; keep mount-pnpm-store while it remains published.

feat: add mount-pnpm-store feature (patched copy of joshuanianji/devc…

…ontainer-features)

Copied at upstream v1.0.2 (commit e91be54). Patch: oncreate.sh exports
PNPM_HOME and prepends $PNPM_HOME/bin to PATH so pnpm >= 9 --global
commands work in non-interactive lifecycle shells (upstream issue #80).