Implement Action Flip Flop Detection in the Publisher

[sidheart]

Issue #: #286

Description of changes:
We don't want to rubber-band when applying Actions (e.g. applying a CPU
increase right after we apply a CPU decrease).

This commit implements logic which allows the Publisher to reject
Actions which flip flop.

Tests:

• TimeExpiringSetTest - Verifies that the underlying TimedFlipFlopDetector collection works as expected
• PublisherTest - Verifies that the publisher rejects flip flopping actions
• TimedFlipFlopDetectorTest - Verifies that the FlipFlopDetector implementation works as expected

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[codecov]

Codecov Report

Merging #287 into master will increase coverage by 0.05%.
The diff coverage is 81.81%.

@@             Coverage Diff              @@
##             master     #287      +/-   ##
============================================
+ Coverage     67.26%   67.31%   +0.05%     
- Complexity     1949     1974      +25     
============================================
  Files           286      288       +2     
  Lines         12712    12766      +54     
  Branches       1034     1040       +6     
============================================
+ Hits           8551     8594      +43     
- Misses         3798     3809      +11     
  Partials        363      363              

Impacted Files	Coverage Δ	Complexity Δ
...ceanalyzer/decisionmaker/actions/ImpactVector.java	81.25% <14.28%> (-18.75%)	10.00 <1.00> (+1.00)	⬇️
...rformanceanalyzer/collections/TimeExpiringSet.java	83.33% <83.33%> (ø)	6.00 <6.00> (?)
...r/decisionmaker/actions/TimedFlipFlopDetector.java	93.75% <93.75%> (ø)	15.00 <15.00> (?)
...anceanalyzer/decisionmaker/deciders/Publisher.java	64.28% <100.00%> (+2.74%)	10.00 <1.00> (+2.00)
...erformanceanalyzer/rca/scheduler/RCAScheduler.java	66.17% <0.00%> (-2.95%)	9.00% <0.00%> (ø%)
...csearch/performanceanalyzer/rca/RcaController.java	81.66% <0.00%> (+0.55%)	39.00% <0.00%> (+1.00%)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 781ae08...f34ed6c. Read the comment docs.

[vigyasharma]

Changes look good, few renaming related comments but good to merge.

[khushbr]

Do you think we will need the resource name for which the flip flop happened ?
So, for for prev = (HEAP: INCREASE, CPU: INCREASE), curr = (HEAP: DECREASE, CPU: INCREASE), we can return HEAP instead of Boolean value ?

What I want to understand is if we use(or might use in future) this information anywhere.

[sidheart]

Since it's trivial to add this information in the future by extracting the logic in this function, I think we can table this until the need arises

[khushbr]

LGTM!