fix: update channel join payload for successful reconnect

[w3b6x9]

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

Channel (subscription) is created with user_token with an expiration that never gets updated with setAuth (never refreshed). No successful reconnection after user_token has expired even though supabase-js is calling setAuth with refreshed token.

What is the new behavior?

setAuth will update each channel's join payload with the latest user_token.

Additional context

Related issue: #123

[acupofjose]

Just to confirm - we are using user_token and access_token for the same token: user_token in the initial join push (and subsequent rejoins) and access_token on an already joined channel?

[w3b6x9]

@acupofjose that’s correct! We’ll consolidate the naming of the token in the future so it’s uniform. Sorry for the confusion!

[kamyker]

I have to say it's a bit weird that for every channel there is additional push call on every heartbeat. That doesn't sound very scalable and multiplexed.

[w3b6x9]

I have to say it's a bit weird that for every channel there is additional push call on every heartbeat. That doesn't sound very scalable and multiplexed.

@kamyker do you mean the additional push as a result of invoking setAuth?

[kamyker]

I have to say it's a bit weird that for every channel there is additional push call on every heartbeat. That doesn't sound very scalable and multiplexed.

@kamyker do you mean the additional push as a result of invoking setAuth?

Yes