fix: don't reconnect a websocket after close()

[annamcallister]

Problem

FireFlyWebSocket.close() isn't terminal. A closed socket can come back two ways:

1. close() never cleared reconnectTimer — only connect() did. Closing during the reconnect backoff leaves the timer running; it later fires and calls connect().
2. reconnect() had no notion of "already closed" — the unexpected-response handler calls it from a deferred stream flush, so a rejection still being drained when close() ran schedules a fresh retry afterwards.

Either way the socket reconnects after the application has closed it and dropped its reference, so nothing is left that can stop it, and it retries every reconnectDelay indefinitely.

Since socketOptions headers are fixed at construction, if the connection was authenticated with a credential that later expires, every retry fails — an endless stream of rejected connections from a socket the application believes is gone.

Fix

A closing flag:

• close() sets it, and clears reconnectTimer
• reconnect() returns early when set
• connect() clears it, so reopening still works

Both halves of close() are load-bearing: the flag stops a future reconnect() call, while the clearTimeout stops an already-scheduled retry — a pending timer calls connect() directly and never goes through reconnect().

connect()'s own reconnectTimer teardown is removed, since close() (called on the line above) now owns it.

[EnriqueL8]

Thanks @annamcallister looks good

[EnriqueL8]

I assume the node-version 24 includes 11.5.1?

[annamcallister]

yes- 24.x should resolve to node 24.21.0/ npm 11.19.0 right now, and obviously only ever go up