[WIP] for limit reduction, duration criteria should depend on next limit's duration

[vidaldid-rte]

Please check if the PR fulfills these requirements

• [X] The commit message follows our guidelines
• [X] Tests for the changes have been added (for bug fixes / features)
• [ ] Docs have been added / updated (for bug fixes / features)

Does this PR already have an issue describing the problem? No

What kind of change does this PR introduce? Limit reduction based on acceptable duration criteria should be applied based on the duration of the next limit.

Usually, the acceptable duration displayed in security analysis is the duration of the next limit. When a reduction is applied to all limits with an acceptable duration of 5 minutes or less, the expectation is that he reduction is applied also to the previous limit (with a duration just higher than 5 minutes) so that the operator is warned in advance.

What is the current behavior? Reduction is applied to the limit with duration in range of the criteria. But this has no effect in term of detected the violation of the previous limit earlier.

What is the new behavior (if this is a feature change)?

• Reduction is applied to the limit with duration in range of the criteria, but also to the previous limit.

• In case two reductions appli to the same limit, the stronger reduction is used (previously, the reduction declared last was applied)

Does this PR introduce a breaking change or deprecate an API?

• [ ] Yes
• [X] No