ci: pass Vite env vars to deploy step so app-level rebuilds pick them up (#11125)

The Build and Deploy steps are separate CircleCI run steps, so inline env vars
in Build don't persist to Deploy. When lerna triggers each app's deploy script
(which re-runs npm run build internally), VITE_LD_CLIENT_ID and friends were
unset, producing a bundle with an empty LD client ID.

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: david-shibley-contentful

.circleci/config.yml

@@ -136,6 +136,9 @@ jobs:
             VITE_ENV='test' \
             REACT_APP_BACKEND_BASE_URL=$BACKEND_BASE_URL_TEST \
             REACT_APP_SLACK_CLIENT_ID=$SLACK_CLIENT_ID_TEST \
+            VITE_GOOGLE_PICKER_API_KEY=$VITE_GOOGLE_PICKER_API_KEY \
+            VITE_GOOGLE_APP_ID=$VITE_GOOGLE_APP_ID \
+            VITE_LD_CLIENT_ID='588a047044b03e0b3211298d' \
             GOOGLE_DOCS_TEST_CLOUDFRONT_DIST_ID=$GOOGLE_DOCS_TEST_CLOUDFRONT_DIST_ID \
             STAGE='test' npm run deploy:test
       - run:
@@ -182,6 +185,9 @@ jobs:
             STATIC_KLAVIYO_S3_BASE="s3://cf-apps-klaviyo/apps" \
             REACT_APP_BACKEND_BASE_URL=$APP_SLACK_BACKEND_BASE_URL_PROD \
             REACT_APP_SLACK_CLIENT_ID=$SLACK_CLIENT_ID_PROD \
+            VITE_GOOGLE_PICKER_API_KEY=$VITE_GOOGLE_PICKER_API_KEY \
+            VITE_GOOGLE_APP_ID=$VITE_GOOGLE_APP_ID \
+            VITE_LD_CLIENT_ID='588a047044b03e0b3211298e' \
             GOOGLE_DOCS_PROD_CLOUDFRONT_DIST_ID=$GOOGLE_DOCS_PROD_CLOUDFRONT_DIST_ID \
             STAGE='prd' npm run deploy
       - run: