fix(installer): hide shell config warnings in CI

[fengmk2]

install.sh now hides shell configuration warnings and instructions when CI=true. CI runners set PATH through the job environment. Changes to shell files do not change later job steps.

The examples show only the relevant output lines.

Before:

warn: Cannot write to /home/runner/.bashrc (permission denied), skipping.
warn: Cannot write to /home/runner/.profile (permission denied), skipping.

Shell configuration:
    - bash: failed ~/.bashrc, ~/.profile

note: Some shells still need manual setup.
Manual setup instructions:

After:

Install locations:
    Data directory: <data-directory>
    Bin directory:  <bin-directory>

Set VP_LOG=trace to show the hidden shell file errors. Installations outside CI keep the warnings and manual setup instructions.

This PR is stacked on #2505.

Closes voidzero-dev/setup-vp#87

[github-actions]

✅ Staging deployment successful!

Preview: https://viteplus-staging.void.app/
Commit: 1ed4e58

[github-actions]

Registry bridge build (7d275a4)

This commit build is published to the registry bridge, which serves these as ordinary npm versions (every other package proxies to npmjs):

Package	Version
vite-plus	0.0.0-commit.7d275a46b5960e82af79a34e6421060c402d1704
@voidzero-dev/vite-plus-core	0.0.0-commit.7d275a46b5960e82af79a34e6421060c402d1704

Install the Vite+ CLI built from this commit, then migrate a project:

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/voidzero-dev/vite-plus/7d275a46b5960e82af79a34e6421060c402d1704/packages/cli/install.sh | VP_PR_VERSION=2511 bash

# Windows (PowerShell)
$env:VP_PR_VERSION="2511"; irm https://raw.githubusercontent.com/voidzero-dev/vite-plus/7d275a46b5960e82af79a34e6421060c402d1704/packages/cli/install.ps1 | iex

Or download the standalone Windows installer built from this commit:

Architecture	Installer
x64	vp-setup-x86_64-pc-windows-msvc.exe
Arm64	vp-setup-aarch64-pc-windows-msvc.exe

GitHub requires you to sign in and downloads each installer as a ZIP artifact. Extract vp-setup.exe, then run it against this preview build:

.\vp-setup.exe --version "0.0.0-commit.7d275a46b5960e82af79a34e6421060c402d1704" --registry "https://registry-bridge.viteplus.dev/"

After installing, upgrade the current project's vite-plus to this test build with:

vp migrate

Or point your package manager at the bridge registry https://registry-bridge.viteplus.dev/:

Package manager	Registry config
npm / pnpm / Bun	.npmrc: registry=https://registry-bridge.viteplus.dev/
Yarn (v2+)	.yarnrc.yml: npmRegistryServer: "https://registry-bridge.viteplus.dev/"

Then pin the build (vite aliases to vite-plus-core; pnpm can use a catalog, npm an overrides entry):

{
  "devDependencies": {
    "vite-plus": "0.0.0-commit.7d275a46b5960e82af79a34e6421060c402d1704",
    "vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.7d275a46b5960e82af79a34e6421060c402d1704"
  }
}

[github-actions]

🐳 Docker preview image

Built from this PR's registry bridge build:

Image	Compressed size
ghcr.io/voidzero-dev/vite-plus:pr-2511	236MB

# remove any stale local copy from a previous run, then pull fresh
docker rmi ghcr.io/voidzero-dev/vite-plus:pr-2511 2>/dev/null; docker pull ghcr.io/voidzero-dev/vite-plus:pr-2511

Quick check:

docker run --rm ghcr.io/voidzero-dev/vite-plus:pr-2511 vp --version

See docs/guide/docker.md for usage.