properties: sanitize newlines ('\n') when exporting ovpn file

Openvpn's ovpn configuration files cannot contain newlines as values,

- the parser reads the ovpn file line by line, splitting lines are
  newlines. Hence, quotation spaning multiple lines is not supported
  to express '\n'.
- special special escape sequences like "\n" or "\012" are not
  supported either. Escape sequences are only for "\'", "\"",
  and verbatim spaces like "\ " (but not newline itself).

Note that newlines can be part of a valid configuration, for example
as part of filenames.

Instead of breaking the line, still try to escape the newline
with "\n".

Previously, openvpn would fail with

    $ openvpn --config my.ovpn
    Options error: No closing single quotation (') in my.ovpn:1

Now, the configuration file has no more such line breaks and openvpn
issues a warning instead:

    $ openvpn --config my.ovpn
    Options warning: Bad backslash ('\') usage in my.ovpn:1: remember that backslashes are treated as shell-escapes and if you need to pass backslash characters as part of a Windows filename, you should use double backslashes such as "c:\\openvpn\\static.key"

The point is not that the warning behavior is better than the error
behavior (it's actually worse). However, I think when writing an
invalid file, it's better to have an invalid escape sequence, than
a spurious line break.

2 jobs for th/export-sanitize-newlines in 5 minutes and 50 seconds (queued for 4 seconds)
Status Job ID Name Coverage
passed #64169


passed #64170