[TIMOB-1952] Android: Escaped ampersand in URI query string gets unescaped thus breaking XHR calls

cf this commit:

http://github.com/appcelerator/titanium_mobile/commit/768616c5f7595b621c75cb35a8abdccb74461f3e"> http://github.com/appcelerator/titanium_mobile/commit/768616c5f7595...

We've had a problem in the past with partially escaped query strings -- unfortunately that commit referenced above does not itself reference a ticket. Anyway, because of partially escaped query strings, we unescape and then re-escape the query string in order to ensure the full string is escaped. But in re-escaping, we do not escape the ampersand because of its status as a field separator. But now this unescape/re-escape causes a problem for query strings that really did want the ampersand escaped.

Fail case app.js:

var URL = "http://www.google.com/m/search?q=test%26junk";
Titanium.UI.setBackgroundColor('#000');
var xhr = Ti.Network.createHTTPClient();
xhr.open('GET', URL);
xhr.send();
Ti.API.info(xhr.location);

When you run that, on the console you'll see that the url becomes http://www.google.com/m/search?q=test&;junk, when it's expected to have that ampersand stay as %26.