feat: add resource and navigation event filtering

[williazz]

Why (updated)

Users currently have no way to filter out unwanted performance events. One story is that customers are receiving a lot of noisy resource events from chrome extensions.

Changes

Users can filter resource events by supplying a ignore(entry: PerformanceEntry) to PerformanceConfig. This enables PerformanceObserver to ignore specified PerformanceResourceTiming entries, which are used to create RUM ResourceEvents.

In addition, ignore() also configures the NavigationPlugin, which uses a PerformanceObserver to create NavigationEvents. Here, customers can look for PerformanceNavigationTiming entries and ignore them if need be.

The default configuration is that only resource events with non-http URL schemas are ignored. This will ignore resource events from browser extensions, which typically follow non-http URL schemas (e.g. "chrome-extension://*").

Revisions

Revision 4:

• fix: remove performance mock data helpers
• fix: remove unecessary defaultIgnore() tests

Revision 3:

• add unit tests for subclasses of PerformanceEntry to verify that only resource events with non-http(s) url schema are ignored by default
• moved unit tests to performance-utils

Revision 2:

• ignore() receives PerformanceEntry
• ignore() is defined in PerformanceConfig and shared between NavigationPlugin and ResourcePlugin. Note: only resource level 2 events are subject to ignoring
• Added unit test to ignore navigation events
• Removed version bump for a separate PR
• Ignore chrome extension events by default
• Rename ignoreEvent() to ignore()
• Remove unrelated refactors

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[ps863]

High level comment: consider updating the description of PR accounting for these new changes in the revisions.

[williazz]

High level comment: consider updating the description of PR accounting for these new changes in the revisions.

updated