Feature/historical conditions

[jvigliotta]

Closes #8082
Closes #8083

Describe your changes:

Adds the ability to evaluate conditions historically.

Majority of the work completed by @khalidadil

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Is this a notable change that will require a special callout in the release notes? For example, will this break compatibility with existing APIs or projects that consume these plugins?

Author Checklist

• Changes address original issue?
• Tests included and/or updated with changes?
• Has this been smoke tested?
• Have you associated this PR with a type: label? Note: this is not necessarily the same as the original issue.
• Have you associated a milestone with this PR? Note: leave blank if unsure.
• Testing instructions included in associated issue OR is this a dependency/testcase change?

Reviewer Checklist

• Changes appear to address issue?
• Reviewer has tested changes by following the provided instructions?
• Changes appear not to be breaking changes?
• Appropriate automated tests included?
• Code style and in-line documentation are appropriate?

[shefalijoshi]

Some more questions and comments.

[shefalijoshi]

Something is wrong with the condition set output when 2 DIFFERENT condition sets are included in a display layout they seem to emit the same output. Even if the expected outputs are different. To reproduce: 1. Create a SWG SWGSmall with a value range of -1 to +1. 2. Create another SWG SWGLarge with a value range of 0 - 20. 3. Create a condition set with a default condition and a 2nd condition where SWGSmall's Sine value > 1 (this should never happen, so it should only output the default output) 4. Create a condition set with a default condition and a 2nd condition where SWGLarge's Sine value > 0 (this CAN happen, so it should NEVER output tte default value) 5. Drag both condition sets into a display layout. 6. Note that both condition sets (alpha numerics) show the same outputs.

[jvigliotta]

Something is wrong with the condition set output when 2 DIFFERENT condition sets are included in a display layout they seem to emit the same output. Even if the expected outputs are different. To reproduce: 1. Create a SWG SWGSmall with a value range of -1 to +1. 2. Create another SWG SWGLarge with a value range of 0 - 20. 3. Create a condition set with a default condition and a 2nd condition where SWGSmall's Sine value > 1 (this should never happen, so it should only output the default output) 4. Create a condition set with a default condition and a 2nd condition where SWGLarge's Sine value > 0 (this CAN happen, so it should NEVER output tte default value) 5. Drag both condition sets into a display layout. 6. Note that both condition sets (alpha numerics) show the same outputs.

So, this was due to an item that was used for output, being removed and the outputTelemetry was not cleared, so it was referencing an item that was removed from the composition, this has been fixed.