The workflow becomes a draft even though no changes have been configured

Current Situation

The value of an argument, node argument or environment variable of a workflow job is an expression.
If this value is empty than it is stored in the JSON as

"my_param_with_empty_value": "\"\""

If the GUI reads "my_param_with_empty_value" then it interprets it as "" instead of "\"\"" and incorrectly assumes that the configuration has been changed.
As a result, the configuration is saved again, causing a deployed workflow to change to draft status even though no changes have been made to the configuration.

Desired Behavior

Only changed configurations should be stored again.