chore: update test-site to use autoinstall from @openedx/frontend-dev-utils

[brian-smith-tcril]

Resolves #160

Removes the local copy of autoinstall tooling from test-site/tools/autoinstall/ and replaces it with the published @openedx/frontend-dev-utils package.

Changes

• test-site/package.json: update dev:autoinstall script to use devutils-dev-with-autoinstall bin with PORT=8080 and FRONTEND_BASE_DIR=..
• test-site/package.json: add @openedx/frontend-dev-utils@^1.0.0 as a devDep, remove chokidar as a direct devDep (now a transitive dep via @openedx/frontend-dev-utils)
• Delete test-site/tools/autoinstall/
• Update root README.md to link to the @openedx/frontend-dev-utils autoinstall docs

Work log

Issue #160: Update test-site to use autoinstall from frontend-dev-utils

#160

Context

The test-site in frontend-base had a local copy of autoinstall tooling in
test-site/tools/autoinstall/. That code has since been extracted and published
as @openedx/frontend-dev-utils@1.0.0. The goal is to remove the local copy and
use the published package instead.

The blocking issue (publishing the package) is closed:
openedx/frontend-dev-utils#4

Key findings

• Published package exposes a devutils-dev-with-autoinstall bin
• The published env.mjs differs from the local one in two ways:
  • FRONTEND_BASE_DIR is now configurable via env var (defaults to ../frontend-base)
  • PORT is now required via env var (throws if not set)
• So dev:autoinstall script needs to pass PORT=8080 and FRONTEND_BASE_DIR=.. explicitly
• chokidar was a direct devDep of test-site; it's now a dep of frontend-dev-utils so can be removed

Changes

Commit 1: update test-site package-lock.json

• Rebuilt the frontend-base tarball (npm run prepack && npm run pack)
• Regenerated test-site/package-lock.json (tarball hash had drifted from what was committed)
• No functional changes

Commit 2: use @openedx/frontend-dev-utils for autoinstall

• test-site/package.json: update dev:autoinstall script to PORT=8080 FRONTEND_BASE_DIR=.. devutils-dev-with-autoinstall
• test-site/package.json: add @openedx/frontend-dev-utils@^1.0.0, remove chokidar as direct devDep
• Delete test-site/tools/autoinstall/ (all 4 files)
• Regenerate test-site/package-lock.json

Investigation: webpack-cli peer:true

While working on commit 2, noticed peer: true was dropping off webpack-cli in the
lock file diff. Investigated whether it was caused by the chokidar → frontend-dev-utils
swap. Confirmed it is NOT — a fresh regen with the original deps (no stash popped) also
drops peer: true and bumps axios 0.30.2 → 0.30.3. Pure npm nondeterminism between runs.

Resolution: amended commit 1 to include the fresh regen (capturing the webpack-cli and
axios noise there), so commit 2's diff is clean and only shows frontend-dev-utils changes.

Status

• Branch created: autoinstall-from-dev-utils
• Commit 1: chore: update test-site package-lock.json to alpha.13 (amended to absorb nondeterminism)
• Commit 2: chore: use @openedx/frontend-dev-utils for autoinstall in test-site
  • Needed FRONTEND_BASE_DIR=.. in the script — published env.mjs defaults to ../frontend-base
    which doubles the path since test-site lives inside frontend-base, not alongside it
• Commit 3: docs: update README to reference @openedx/frontend-dev-utils autoinstall
• Branch pushed to fork
• PR opened