[Direct Binary Access] DataRecordDownloadOptions creates invalid Content-Disposition headers - Workaround

DataRecordDownloadOptions always adds the extended parameter filename* to the header, without any escaping.

Such extended parameters must not include spaces (and only a small predefined list of basic ascii chars), otherwise they have to be percent encoded. The RFC is https://tools.ietf.org/html/rfc5987 and note the definition of value-chars in the grammar.

Because of this, if a filename includes a space or another character that must be percent encoded, this currently creates an invalid header that fails to be parsed by other clients.

See also https://github.com/jshttp/content-disposition/issues/24