The original goal of the bug was to merely use the `PerformanceTestingHelper.dispatch` method to trigger these new performance measurement times, but Gandalf brought to my attention that he has a use for these same events outside of performance testing. This is what lead us to standardize the event names more concretely, and instead trigger them using `window.dispatchEvent`. Now they can be used in more than just performance testing, and more importantly, don't depend on the performance script in order to trigger the events.

We do not plan to remove the transmission of custom events specific to individual apps.