Provide config options to load js and css as binary instead of text

[peterskim12]

By default, the MarkLogic treats javascript (.js) and css (.css) files as 'text'.

It'd be nice to have a Roxy deployer configuration option to load these assets as binary instead of text because I often run into issues where a .js or .css file may be encoded in some foreign encoding and throws an exception during Roxy deployment.

I can think of a few options for handling this:

1. Provide load-js-as-binary and load-css-as-binary configuration options with valid options of true and false.
2. Piggyback on the existing load-html-as-xml configuration; if this false, then assume that the user is probably using MarkLogic as an HTTP web server to serve static assets and that they'd want js and css files to be treated as binary.
3. Support a more complex configuration map where a user can configure N number of mime-type/extension/format configurations.

[dmcassel]

I lean toward 1), with default.properties defining them as true. I'd imagine that with html, js, and css, we've probably about got the problem cases covered. I think finding one more should trigger option 3.