Fixes #23607: When a mandatory field in a technique is not defined, we can save a technique and we have a nasty error

[amousset]

https://issues.rudder.io/issues/23607

In 8.0, rudderc has (inadvertently) changed the output format from a list of plain strings to a list of

{
  "name": "optional",
  "value": "previous value"
}

And regex from a string to:

{
  "error_message": "optional",
  "value": "previous value"
}

This change was not expected in the webapp, but the parser for this file was rewritten at the same time, with a typo on the constraint key name (constraint instead of constraints), which lead to totally ignoring constraints (and hide the error).

As the change in rudderc was made to improve consistency with select parameter type in techniques, this PR changes the expected format on the webapp side. We can do this as rudderc and the webapp come in the same package and are always in sync.

This PR fixes the checks on parameters in the editor:

Also adding an annotation in rudderc to avoid the null error_message in regex:

"regex": {
    "value": "^[A-z0-9._-]+$",
    "error_message": null
}

[amousset]

PR updated with a new commit

[amousset]

PR updated with a new commit

[amousset]

PR updated with a new commit

[Normation-Quality-Assistant]

This PR is not mergeable to upper versions.
Since it is "Ready for merge" you must merge it by yourself using the following command:
rudder-dev merge https://github.com/Normation/rudder/pull/5118
-- Your faithful QA
Kant merge: "It is beyond a doubt that all our knowledge begins with experience."
(https://ci.normation.com/jenkins/job/merge-accepted-pr/75253/console)

[amousset]

OK, squash merging this PR