Issue to fix

Before the race conditions happens when rumAgentLoop (running on task thread) try to create rumScope, while at the same time startView is called from BrightScript main thread, they enter in the if block ensureRumScope almost` the same time, causing two scopes are created, thus customers will see two session in the explorer, one containing only the first view with very short duration, the other is normal.

How this fix works

instead of directly triggering ensureRumScope from the thread of callsite, we send the event to the port of this task to which the task is always listening, once rumAgentLoop receives the event, it will be handled always in the task thread.

Additional Notes

Some other fix:

• Remove periodic KeepAlive event in rumAgentLoop since it's a outdated concept
• Fix a log

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Make sure you discussed the feature or bugfix with the maintaining team in an Issue
• Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)