Partial support of HvdcAction

[annetill]

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

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

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

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

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)

[geofjamg]

Looks good.
Note for later: Our LfAction is begin to be messy. As it is now responsible for many different actions we probably need to design a hierarchy of LfAction instead of putting everything into just one.

[annetill]

Looks good. Note for later: Our LfAction is begin to be messy. As it is now responsible for many different actions we probably need to design a hierarchy of LfAction instead of putting everything into just one.

Yes, but it is also what we are doing for LfContingency, so you want to refactor this class too?

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

97.4% Coverage
0.0% Duplication