subscribeBalanceUpdates sends incorrect events

[alexander-hagen]

Describe the bug
After succesful subscription to subscribeBalanceUpdates, the socket sends incorrect event messages.

Expected message is:
{
"e":"BALANCE",
"x":"OutboundAccountPositionOrderEvent",
"E":1635515839203,
"I":208810488108744704,
"i":1635515839203,
"B":[
{
"a":"btr",
"F":"9999999.9658620755200000",
"T":1635515839000,
"f":"2.8125000000000000",
"L":"0.0000000000000000",
"l":"-2.8125000000000000",
"t":1635515839000
},
{
"a":"usdt",
"F":"10000008.8000000000000000",
"T":1635515839000,
"f":"10.2600000000000000",
"L":"0.0000000000000000",
"l":"-10.2600000000000000",
"t":1635515839000
}
],
"u":1090862
}
Actual message is:
{ event: 'user_balance_update', status: 'ok', ts: 1707595503038 }

To Reproduce
Steps to reproduce the behavior:

1. Open a websocket with api keys and valid token
2. Once authenticated, 'subscribe to Balance Updates'
3. See error

Expected behavior
After subscribing to Balance Updates the correct response should be given

[alexander-hagen]

It might be that if there are no balance updates, the event does not contain a payload. To validate this it needs a balance on the exchange to allow order creation.