Describe the current behavior

Currently, HvdcRangeActionImpl::apply() automatically deactivate the ac emulation even if the set point was not optimized. Plus as is we can't hvdc range action can't be optimized and can only be used as auto RA.

Describe the expected behavior

1. We don't want to automatically deactivate acEmulation and the apply won't have any impact of the line if acEmulation is on (as it doesn't make any sense)
2. We expect to have a network action that will deactivate ac emulation (it would like any other network action) and only if the acEmulation is off on the hvdc line we can optimize the set point in MIP.

Describe the motivation

To be able to optimize set point and deactivate ac emulation when it can improve the situation

Extra Information

No response