Add abort functionality to Telemetry Collection requests and "getLimits"

[jvigliotta]

Is your feature request related to a problem? Please describe.
Regular telemetry requests will abort on navigation. Telemetry Collection requests only abort when destroyed, which is dependent on the view that created the collection and the load on the UI at the time. We should also have a backup that will cancel on navigation for Telemetry Collection requests.

Requests for limits are asynchronous and should also support aborting on navigation as they are initiated from the Telemetry API and the groundwork is already there to support this.

Describe the solution you'd like
Abort'n

Describe alternatives you've considered
Not abort'n

[jvigliotta]

Testing

• throttle your network in the dev console network tab
• go to a view that uses Telemetry Collections (Telemetry Table, LAD, etc) and a view that requests limits (Overlay Plot)
• go to the view, nav away before requests have completed
• observe requests for limits have been cancelled as well aa requests triggered from a Telemetry Collection view

[akhenry]

Please also verify that the errors reported in VIPEROMCT-386 are also resolved. If not, file a separate issue to fix.

[michaelrogers]

This fix is verified during testathon 10/03/23. Telemetry collections and overlay plots stop trying to make fetch happen when navigating away.

Though I am seeing the AbortError Dave observed in VIPEROMCT-386.

@ozyx - should I file a separate issue for this?