[Bug] Fern login fails on AL2003 / Node18

[Chaffelson]

Describe the bug

Attempting to using Fern on AL2003 as a development environment fails.

[ec2-user@ip-172-31-9-254 fern_test]$ fern login
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: spawn xdg-open ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:284:19)
    at onErrorNT (node:internal/child_process:477:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ChildProcess instance at:
    at ChildProcess._handle.onexit (node:internal/child_process:290:12)
    at onErrorNT (node:internal/child_process:477:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn xdg-open',
  path: 'xdg-open',
  spawnargs: [
    'https://fern-prod.us.auth0.com/authorize?client_id=<snip>&response_type=code&connection=github&scope=openid+profile+email+offline_access&redirect_uri=http%3A%2F%2Flocalhost%3A3129&audience=venus-prod'
  ]
}

Node.js v18.20.4
Fern 0.44.11

To reproduce

Steps to reproduce the behavior:

1. Deploy AL2003 server
2. Setup for SSH development with Visual Studio Code or Cursor or similar
3. Install node 18
4. install fern
5. run fern login

If relevant, provide a minimal API definition (OpenAPI or Fern Definition) or Docs configuration (docs.yml) that can be used to reproduce the error.

Expected behavior

Login should succeed, or at least not throw an error.