Properties editor for jobs should consider the type of the given values

Current Situation

The environment variables for jobs do have a name and a value. The value is an expression. The gui provides an editor to define the name and the expression.

When enter an expression the editor creates this json.

value a ==> "x": "'a'",
value 1 ==> "a": "'1'",
value true ==> "c": "'true'",
value pre $js7OrderId post ==> "d": "pre $js7OrderId post"

When reading the properties from the json the editor shows.

value a ==> 'a'
value 1 ==> '1'
value true ==> 'true'
value pre $js7OrderId post ==> pre $js7OrderId post

When the value is pre $js7OrderId post the workflow becomes invalid.

Desired Behavior

When entering an expression in the editor for job environment variables creates this json.

value a ==> "x": "'a'",
value 1 ==> "a": "'1'",
value true ==> "c": "'true'",
value pre $js7OrderId post ==> "d": "\"pre $js7OrderId post\""

When reading the properties the editor shows.

value a ==> '1'
value 1 ==> 1
value true ==> true
value pre $js7OrderId post ==> "pre $js7OrderId post"

When the value is pre $js7OrderId post the workflow should remain valid