Avoid excessive reexecution of useSendTelemetry.

[dennisoelkers]

Description

Motivation and Context

This PR is optimizing useSendTelemetry for minimal reexecutions. Previously, the hook was reexecuting on every route change, due to useLocation in useRoutePattern triggering a rerender. In many cases this was unnecessary, as the returned location would on be used when the telemetry function that is produced is actually executed.

Therefore, this change is now pushing the route parsing into the generated function, so it does not need to be regenerated when the route changes. As the hook is consumed in many places and its reexecution and constant regeneration of the function it produces, this change is avoiding cascading rerenders.

/nocl No user-facing change.

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (non-breaking change)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.

[ousmaneo]

LGTM!