Fix "No such edge in graph" exception

[geofjamg]

Please check if the PR fulfills these requirements (please use '[x]' to check the checkboxes, or submit the PR and then click the checkboxes)

• 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)

Does this PR already have an issue describing the problem ? If so, link to this issue using '#XXX' and skip the rest
No

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix

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

With so kind of node/breaker topology with a switch loop we can have an exception like this:

Caused by: com.powsybl.commons.PowsyblException: No such edge in graph: BR1
	at com.powsybl.openloadflow.graph.EvenShiloachGraphDecrementalConnectivity.cut(EvenShiloachGraphDecrementalConnectivity.java:92)
	at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
	at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:179)
	at java.base/java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1707)
	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
	at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
	at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)
	at com.powsybl.openloadflow.network.impl.PropagatedContingency.toLfContingency(PropagatedContingency.java:289)
	at com.powsybl.openloadflow.sa.AcSecurityAnalysis.runSimulations(AcSecurityAnalysis.java:145)
	at com.powsybl.openloadflow.sa.AcSecurityAnalysis.runSync(AcSecurityAnalysis.java:85)
	at com.powsybl.openloadflow.sa.AbstractSecurityAnalysis.lambda$run$0(AbstractSecurityAnalysis.java:88)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at com.powsybl.computation.CompletableFutureTask.run(CompletableFutureTask.java:44)
	at java.base/java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(ForkJoinTask.java:1395)
	at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182)
	at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655)
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622)
	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)

Remark: the disconnector in the loop is also required to get the exception and breaker has to be "retained".

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

This case is expected to be working well.

Does this PR introduce a breaking change or deprecate an API? If yes, check the following:

• The Breaking Change or Deprecated label has been added
• The migration guide has been updated in the github wiki (What changes might users need to make in their application due to this PR?)

Other information:

(if any of the questions/checkboxes don't apply, please delete them entirely)

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication