[MultiYAxis] Activating Limit lines on a series fails

[ozyx]

Summary

Expected vs Current Behavior

Limit lines should be able to be activated, settings should persist per series, and limit lines should be displayed correctly.

Steps to Reproduce

1. Create an Overlay Plot
2. Create a SIne Wave Generator
3. Drag it into the Overlay Plot
4. In Edit mode on the Overlay Plot, edit the series settings and activate "Limit Lines"
5. Observe console errors
6. Observe no limit lines appear
7. Save, navigate away and back, edit again and notice the settings have not persisted

Environment

• Open MCT Version: feature/plots-multiple-y-axes
• Deployment Type: local
• OS: MacOS
• Browser: Chrome

Impact Check List

• Data loss or misrepresented data?
• Regression? Did this used to work or has it always been broken?
• Is there a workaround available?
• Does this impact a critical component?
• Is this just a visual bug with no functional impact?
• Does this block the execution of e2e tests?
• Does this have an impact on Performance?

Additional Information

[shefalijoshi]

Testing instructions:

1. Create an overlay plot with multiple telemetry endpoints with different ranges and/or limits (For Sine Wave generators, use different offsets)
2. Enable limit lines for all endpoints in the inspector properties
3. Ensure that limit lines are drawn correctly and hovering over the legend shows limit values
4. Move the telemetry endpoints between y axes
5. Ensure that limit lines are drawn correctly and hovering over the legend shows limit values
   NOTE Depending on the telemetry endpoint, sometimes the limits might be outside the canvas and may not be drawn.

VIPER Deployment
Validate the above with the /ViperGround/Test/navcamPanAngle endpoint. Reach out to @unlikelyzero if you have additional problems

[ozyx]

Verified fixed Testathon 1-31-23