Avoid another csv parser trap (backslash)

As far as I understand it, the problem is mostly that different
tools in our chain use different escaping conventions for csv.

CSV is probably a silly format to use at the end of the day, but
it's so temptingly compact for feature files.
STAC features: extract separate (e1,e2) (e2,e1)

Previously we working in a non-directional fashion.
Which was silly