Add category keys to Parameters

[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?

Some category keys are added:

• VoltageControls, GeneratorVoltageControl, TransformerVoltageControl, ShuntVoltageControl.
• ReactivePowerControl
• PhaseControl
• SlackDistribution
• ReferenceBus
• LowImpedanceBranch.
• NewtonRaphson, NewtonKrylov.
• FastRestart
• OuterLoops
• Dc.

Some keys are missing for automaton systems, secondary voltage control, AC solver type, load model, line per unit mode, asymmetrical calculations, extra reported features, debug directory, min and max realistic voltages, voltage init override

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[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[jeandemanged]

very nice! some suggestions:

• dc move from category DC to Solver: then we can see in one place if it is DC, NR, NK
• PerUnit category: I would remove this category and merge it in Model (only linePerUnitMode)
• reportedFeatures, I would create a new Reporting category, this is not debug.
• Maybe move the NewtonRaphson params related to state vector scaling in a dedicated category NewtonRaphsonStateVectorScaling (5 parameters), all other parameters remaining in NewtonRaphson would then be related to stopping criteria.

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
99.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[geofjamg]

very nice! some suggestions:

• dc move from category DC to Solver: then we can see in one place if it is DC, NR, NK
• PerUnit category: I would remove this category and merge it in Model (only linePerUnitMode)
• reportedFeatures, I would create a new Reporting category, this is not debug.
• Maybe move the NewtonRaphson params related to state vector scaling in a dedicated category NewtonRaphsonStateVectorScaling (5 parameters), all other parameters remaining in NewtonRaphson would then be related to stopping criteria.

Done for perunit et reportedFeatures.

• DC: DC mode is not only a solver change but above all a modelling change with different equations. This is different that changing a solver like NR, FDNR, NK, GS running on same AC equations.
• NewtonRaphsonStateVectorScaling that would required to make it clean to have some kind of subcategory feature in parameters.

[annetill]

Looks good!