…e field

When a docker-compose.yaml includes a top-level 'name:' field, the
compose-go loader attempts to assign to ConfigDetails.Environment which
is nil, causing a panic.

Initialize the Environment map to an empty map before calling the loader.

Fixes #2970

…med-project

fix: prevent nil map panic when docker-compose.yaml has top-level name field

Signed-off-by: Ryan Swanson <ryan.swanson@loft.sh>

…amic HTTP responses

- add per-run build markers to restarthelper fixtures to avoid cached image reuse
- retry sync writes until the remote file reflects the change instead of assuming watcher readiness
- sanitize terminal output parsing so pod name detection is resilient to control characters
- deduplicate image tag lookup logic in build tests
- clean up env var set/unset handling across e2e tests to satisfy errcheck

- lazy-load node-fetch, cli-spinner, inquirer, and find-process in dist/npm/index.js
- switch get-latest to built-in https so it can run without local node_modules
- keep postinstall working when find-process is not yet installed
- prevent npm global install from failing during prepare/postinstall in a clean checkout

Signed-off-by: Ryan Swanson <ryan.swanson@loft.sh>

- lazy-load optional installer dependencies in dist/npm/index.js
- use built-in https for latest-version lookup and release downloads
- fall back to plain logging when cli-spinner is unavailable
- keep finish-install working without local node_modules in clean checkouts
- teach npm launcher scripts to resolve index.js from the npx temp package layout
- preserve existing global npm and yarn fallback lookup behavior

* Adds check for websocket source
* Updates go toolchain
* Various fixes for unit and e2e tests
* Fixes for npm installation