setCommand in nimble task does not correctly parse `--define:MyFlag="blablub"` flag, adds linefeed as prefix

[PhilippMDoerner]

Minimal example:

#project.nimble
task play, "Build a release for debugging":
  --define:basePath:"lalalu"
  --outdir:"."
  setCommand "c", "src/playground.nim"

#project.nim
const basePath {.strdefine.} = "path from file not from flag"

echo "Basepath ",basePath

Expected output: Basepath lalalu or Basepath "lalalu"

Received output: Basepath \x0A "lalalu"

Possibly related to #929 and/or #723 The character it adds appears to be a line-feed character? http://daleswanson.org/ascii.htm