[Performance] Check views for memory leak on navigation

[akhenry]

There is a class of memory leak that occurs where references to view objects are retained even after the view has been destroyed. View destruction occurs on navigation.

The usual reason for this is a failure to clean up event handlers.

This can cause performance degradation of the application over time as memory builds up. This is a particular issue with views that hold onto historical telemetry.

A draft PR exists that provides a framework for implementing this kind of test. It should be configured to run on every PR to catch memory leaks as soon as they are introduced. The draft PR defines tests for the following object views:

• Overlay Plots
• Stacked Plots
• Tables
• LAD Tables
• LAD Table Sets
• Imagery View (Except for CompassRose)
• Simple Display Layouts
• Simple Flexible Layouts
• Notebooks
• Tabs View
• Condition Widget
• Timeline View

Filed followup for remaining screens - #6734
Also see: #4209

[shefalijoshi]

Testing Instructions:

• Retest Display Layout actions
• Retest Drawing tools for display layouts - Box, Line, Ellipse, Text, Image
• Retest resizing display layouts
• Retest Flexible Layout actions - Rukmini
• Retest Plot limit lines - John
• Plot annotations (including searching for annotations and clicking on search results) - Jesse
• Data Pivoting (getting here should touch a lot of other components) - Dave