Modify leaf get range actions method

[MartinBelthle]

Please check if the PR fulfills these requirements

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

A PR modifying a real test case has been opened on farao-cucumber repository

Does this PR already have an issue describing the problem ?

• [FAR-837] Investigate Leaf getRangeActions() method

• This also solves the second issue of the 2 described in the internal Confluence page : "Sujets en cours", on the SWE case.

What kind of change does this PR introduce?

Bug fix.

What is the current behavior? (You can also link to an open issue here)

Current method :

@Override
public Set<RangeAction<?>> getRangeActions() {
    if (status == Status.EVALUATED) {
        return prePerimeterActivationResult.getRangeActions();
    } else if (status == Status.OPTIMIZED) {
        return postOptimResult.getRangeActions();
    } else {
        throw new FaraoException(NO_RESULTS_AVAILABLE);
    }

prePerimeterActivationResult.getRangeActions() returns every available range action in the CRAC.
On certain conditions described in the Confluence page, postOptimResult.getRangeActions() returns the same thing.

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

New method:

@Override
public Set<RangeAction<?>> getRangeActions() {
    if ((status == Status.EVALUATED) || (status == Status.OPTIMIZED)) {
        return optimizationPerimeter.getRangeActions();
    } else {
        throw new FaraoException(NO_RESULTS_AVAILABLE);
    }

The getRangeActions() method now only returns the rangeActions that belong to the optimizationPerimeter and only these ones.

Does this PR introduce a breaking change?

No