fix(auth): read axios error status from e.response, not e.status

[SafraNako]

Fixes #51

What

getWorkerRegistrationStatus() in src/auth/registry.ts branches on e.status,
but axios@1.7.9 (pinned) puts the HTTP status on e.response.status — the
top-level e.status alias was only added in axios 1.8.0. So e.status === 404
is always false and both 404 branches are unreachable:

• a not-yet-registered worker's 404 WorkerNotFoundException returns ERROR
  instead of NOT_EXISTS, so registerWorker() never reaches
  storeWorkerInRegistry() and loops forever under promiseRetry({ forever: true });
• the empty-body 404 "invalid path" branch is also dead.

Change

• Read status / data from e.response?.… in the getWorkerRegistrationStatus
.catch, so the NOT_EXISTS and "invalid path" branches work again.
• logger.error(e.data) → logger.error(data) (was always logging undefined).
• Guard the e.response.data reads in the .catch handlers of
  storeWorkerInRegistry and obtainTokenFromAuthServer (src/auth/login.ts) —
  on a network-level error e.response is undefined and e.response.data
  throws a TypeError from inside the catch, masking the real error.

Matches the existing e.response?.status pattern in src/util/base-urls.ts.

Notes

Behaviour-only fix, 2 files. The repo has no test suite (npm test is a stub), so
this is covered by inspection. Verified prettier --check passes on both files.

🤖 Generated with Claude Code