[CT-1898] Turn on event tracking integration testing

[kwigley]

Describe the bug

We turned off event-tracking integration tests because of non-deterministic behavior leading to flakey tests. We should set up the tests so that they confirm event tracking is working properly and handle the fact that sometimes different events are fired randomly.

AC
Select a single tracking event and re-write the test harness in such a fashion that it's reliable (using Python's built-in web server and overriding the Tracker Emitter endpoint as one idea).

An additional ticket will be made to test additional events in the same way.

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest; add a comment to notify the maintainers.

[ChenyuLInx]

@aranke found that tracking tests are commented out because of this issue.
#5527 refactors the tracking, it might be worth looking into reopen this one or write new tracking tests