Connectivity data in DC sensitivity analysis

[annetill]

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)

Does this PR already have an issue describing the problem?

No.

What kind of change does this PR introduce?

In a DC sensitivity analysis, we have a connectivity analysis to determine the breaking connectivity elements. The method to determine them first select candidates for connectivity break, but some of them can be removed because there are not breaking connectivity. If we have some of them, we have to update the connectivity with only breaking connectivity elements.

What is the current behavior?

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

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

• Yes
• No

If yes, please check if the following requirements are fulfilled

• The Breaking Change or Deprecated label has been added
• The migration steps are described in the following section

What changes might users need to make in their application due to this PR? (migration steps)

Other information:

[sonarcloud]

Quality Gate failed

Failed conditions
89.5% Coverage on New Code (required ≥ 90%)

See analysis details on SonarCloud

[annetill]

Thanks!