Improper use of EventEmitter [violation of RTC10]

[sacOO7]

• As per RTC10, library must not register any listeners for internal use.
• At most of the places, ably-ruby uses emitter callbacks to detect state changes and execute internal code.
• This is causing problems in order of code execution with respect to internal and external code. Same is being reflected in flaky behaviour of the tests. To mitigate this flaky test behaviour, usage of EventMachine.next_tick can be found in the emitter callbacks. But, this is not a proper solution for apps running in production.
• We have fixed one of the similar issue as a part of https://github.com/ably/ably-ruby/pull/416/commits/a3d97462dadeae573d0b5190229b28d4c92368cb.
• Aim of this issue is to find and implement code without emitter callback registrations.

┆Issue is synchronized with this Jira Task by Unito

[sacOO7]

One of the solution would be to use internalEmitter that's specific to internal library. We use the same in case of ably-go https://github.com/ably/ably-go/blob/0885021e9c92c9895dfbeb644e71fa45936cd4ae/ably/realtime_conn.go#L1016 and https://github.com/ably/ably-go/blob/0885021e9c92c9895dfbeb644e71fa45936cd4ae/ably/realtime_channel.go#L1028