Update deps and clean quickstart drift

[dex-the-ai]

Summary

• Update the Node quickstart dependencies from current master and refresh the lockfile.
• Remove stale setup scripts and unused env example fields that no longer match the repo.
• Clarify the README local setup snippet so it explicitly starts from config/dev.env.example and includes DB_BUCKET_NAME.

Verification

• fnm use 20 && npm install
• npm test ✅ (19/19)
• npm start + manual API walkthrough on localhost ✅

Evidence

• Fresh rerun from master passed the Jest suite on Node 20.

• Walkthrough exercised airport list/direct-connections, airline list/to-airport, and full airport/airline/route CRUD against the running app.

• README/env drift fixed: the repo no longer advertises IS_CAPELLA / DELAY, and the setup snippet now tells readers to copy config/dev.env.example before editing.

• `

  Walkthrough result summary

  • airport/list → 200 (Abbeville sample)
  • airport/direct-connections → 200 (AAE sample destination)
  • airline/list → 200 (40-Mile Air sample)
  • airline/to-airport → 200 (Air France sample)
  • airport CRUD → 201/200/200/204
  • airline CRUD → 201/200/200/204
  • route CRUD → 201/200/200/204
  `

• tutorial-maintenance/runs/couchbase-examples__nodejs-quickstart/2026-04-29-fresh-from-main/verification.md

• tutorial-maintenance/runs/couchbase-examples__nodejs-quickstart/2026-04-29-fresh-from-main/commands.txt

Notes

• The old init-db / init-test-db / init-test-index scripts still referenced missing files on master, so this PR removes those dead entry points instead of leaving them advertised.
• I kept the evidence text-first for this fresh rerun; richer Swagger media is possible for this repo, but the log/request proof here already covers the user-facing flow clearly.

[gemini-code-assist]

Code Review

This pull request updates project dependencies, removes unused packages, and simplifies the configuration by removing several database initialization scripts. The README has been updated with instructions for setting up the local environment. A suggestion was made to include the setup command for the test environment file to ensure that local integration tests can be executed without missing configuration errors.

[gemini-code-assist]

The npm test script in package.json is configured to use ./config/test.env. Since you are now explicitly instructing users to create config/dev.env from the example file, you should also include the command to create config/test.env. This ensures that users can run the integration tests locally without encountering errors about missing environment files.

Suggested change

	cp config/dev.env.example config/dev.env
	cp config/dev.env.example config/dev.env
	cp config/test.env.example config/test.env