refactor (akka-apps): Switching from Meteor to GraphQL to determine whether user is connected

[gustavotrott]

This update focuses on enhancing the system's method of tracking user connection status, as part of the broader initiative to migrate away from Meteor. Traditionally, a user's connection status was determined by their interaction with Meteor. However, this change proposes leveraging GraphQL connections for this purpose.

The essence of this pull request is to shift the basis for marking a user as disconnected from their Meteor interactions to their activity with GraphQL connections. It introduces a system that actively observes a user's engagement with GraphQL. A user's connection will be registered upon connecting through GraphQL, and should they terminate all such connections, the system will mark the user as disconnected. This status change triggers the removal of the user from the room after a 30-second delay, maintaining consistency with the current functionality but without dependency on Meteor.

Note: The user.disconnected status is a rebranded version of what was previously known as leftFlag.

screen-recorder-fri-feb-09-2024-09-31-53.webm

[sonarcloud]

Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[github-actions]

Automated tests Summary

✅ All the CI tests have passed!

[gustavotrott]

In order to work properly, it requires a subsequent PR removing the Meteor routines that monitor the user connections and perform some actions like Join/Leave, once now it will be monitored by Graphql connections.
cc @Tainan404