Fix/BEAM-3815 - Switching accounts too fast throw error with HeartBeat

[gabrielbeamable]

Attempt to fix issue with heartbeat erroring while users are being changed

Ticket

https://disruptorbeam.atlassian.net/browse/BEAM-3815

Brief Description

If you change users fast enough and while the SDK is sending a HeartBeat to the server, it's possible to get
an error where it complains that the user being sent by the HeartBeat is not the actual user.

Now we are waiting for an user change to happen before sending the heartbeat. The error still might occur in
the case that, for some weird reason not found yet, the heartbeat was send before the user start changing, and
somehow the change happens before the heartbeat finishs.

Checklist

• Have you added appropriate text to the CHANGELOG.md files?

Add those to list or remove the list below altogether:

• Have you included a docs file as /wiki/BEAM-1234.md? You need to provide a docs file.

Notes

When you are merging a feature branch into main, please squash merge and make sure the final commit contains any relevent JIRA ticket number. If you are merging from main to staging, or staging to production, please use a regular merge commit.

Does this introduce tech-debt? If so, have you added an entry to the Tech-debt document?

[gabrielbeamable]

Not sure if this is worth adding a line to the changelog, what do you think?

[github-actions]

Lightbeam link

[cdhanna]

I like this- but I'm not convinced we should merge it without a better understanding of what is happening. I know that sucks, and it means this PR is going to sit dormant for most of the sprint. I want to make sure we feel confident in the code we push into main.