fix: BotServer

[luanluciano93]

• several people have reported issues with v8 recently. The problem originates from the botserver and this PR fixes it!

credits: @Leesneaks

[Leesneaks]

There's also an issue where the Bot server doesn't clear out the websockets on clear() as it .cancel(socket) where socket is always 1, yet the index is the actual operation ID.

This makes sure it clears it from HTTP.operations as well.
The next connection will still keep the older index as this is done within the client int operationId = m_operationId++;

I've had no issues with it.
Leesneaks/otclientv8@119f93d

[Leesneaks]

@luanluciano93 I removed the onopen.
Whilst it works,, whilst updating my botserver, I noticed there's a way to crash people (not instantly) via BotServer and it'll cause an infinite loop spamming the warn messages.

I updated it slightly in this Leesneaks/otclientv8@a5a2661
by using onError to look for resolve error, this way if it can't connect it'll just stop trying. rather than looping.
This works well for me, but i could see some issues with people with bad internet having an issue or two.

Could be modified to try to reconnect a few times on resolve error, rather than 10x but thats down to whoever wants to include it.