Scripts and processes bug

[YanaDePauw]

The REST code for the scripts and processes does not take into account the "hasArg" value of the configured script options.
Instead, the REST API only exposes the option type. I believe angular will then use this option type to force an argument or not depending on the type.
When the type is a String, which is the default type, an argument will be forced.

As a consequence, when no argument needs to be provided, the type needs to be changed to a boolean as is done here.

This is very unintuitive when adding configuration for new scripts.

This bug was noticed in the review of the harvest script.

Expected behavior

Ideally, the converter should set the type to boolean when no other type is provided and when there should be no argument provided for the parameter instead of having to set the type manually for every parameter.

Related work

This issue was noticed when reviewing the Control collection harvest from the UI PR.