Add support to optionally configure the events used for detecting and handling when page unload and flushing occurs

[MSNev]

Some users have specific requirements to minimize the amount of time required to process requests during page navigation.

When the SDK hooks the 'beforeunload' event this can cause Chromium based browsers to delay (around 30ms) the start of the page navigation when the user starts typing in the browsers URL.

The enhancement is to add support to allow the fine tuning of which events should be excluded (if possible) from the page unload (auto flushing) process. The SDK must ensure that it hooks at least one of the required events even if required based on the runtime environment

Configuration Proposal

disablePageUnloadEvents?: string[];
[Optional] An array of the page unload events that you would like to be ignored, special note there must be at least one valid unload event hooked, if you list all or the runtime environment only supports a listed "disabled" event it will still be hooked, if required by the SDK.
Unload events include "beforeunload", "unload", "visibilitychange" (with 'hidden' state) and "pagehide"

disablePageShowEvents?: string[];
[Optional] An array of page show events that you would like to be ignored, special note there must be at lease one valid show event hooked, if you list all or the runtime environment only supports a listed (disabled) event it will STILL be hooked, if required by the SDK.
Page Show events include "pageshow" and "visibilitychange" (with 'visible' state)

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.