[PATCH] Fix generated html for remote_function so that ampersands can be used in passed in options

The following code before this patch produced the following html...

<%=
tmp = "'object[name]=' + result + '&object[attr1]=' + attr1 + '&object[attr2]=' + attr2"
remote_function :url => objects_path, :method => :post,
  :with => tmp.html_safe
%>

new Ajax.Request('/objects', {
  asynchronous:true, evalScripts:true, method:'post',
  parameters:
    'object[name]=' + result + '&object[attr1]=' + 
    attr1 + '&object[attr2]=' + attr2 + '&authenticity_token=' +
    encodeURIComponent('YAq5IJ6Cbfcy3Faebh3gJFKXiba9L87RB0i7m2fEmpg=')
})

Note the escaping of &'s to &

Without the patch the entire "Ajax..." string is unsafe due to concatenations of various options and strings even if we pass our parameter string as html_safe; an html_safe string concatenated with an unsafe string results in an unsafe string. Since our end result will always be an unsafe string the resulting javascript is escaped causing the invalid results to be produced.

With the patch, because the entire javascript string is made html_safe, we don't need to specify html_safe for our own string, so the following code...

<%=
remote_function :url => objects_path, :method => :post,
  :with => "'object[name]=' + result + '&object[attr1]=' + attr1 + '&object[attr]=' + attr2"
%>

now results in the correct output of...

new Ajax.Request('/objects', {
  asynchronous:true, evalScripts:true, method:'post',
  parameters:
    'object[name]=' + result + '&object[attr1]=' + attr1 + 
    '&object[attr2]=' + attr2 + '&authenticity_token=' +
    encodeURIComponent('YAq5IJ6Cbfcy3Faebh3gJFKXiba9L87RB0i7m2fEmpg=')
})