Improved memory usage in Espruino

Neither of these issues turned out to be specific to the improved memory usage builds.

Okay, the BMP gives bogus results on the normal firmware too - Looks like it must have been the 32bit int change.

The http response is mondo mangled - same way every time, and it comes out correctly when viewed in a normal browser, and worked correctly in v65. So somewhere between v65 and v68, there's been a really nasty regression in http. (note - these are being tested with Wiznet)

function getfargostatus() {
	var fargost="";
	require("http").get(fargosturl, function(res) {
		res.on('data',function (data) {fargost+=data;});
      res.on('close',function() {console.log(fargost); var tfs=JSON.parse(fargost); vtfs=tfs; for (var i=0;i<8;i++) { fargo[i]=tfs.relaystate[i].state;} if(menustate==3){uplcd();}});
	});
}

Expected result:

{"relaystate":[ {"state":1,"rdtiev":0}, {"state":1,"rdtiev":0}, {"state":0,"rdtiev":0}, {"state":0,"rdtiev":0}, {"state":1,"rdtiev":0}, {"state":0,"rdtiev":0}, {"state":0,"rdtiev":0}, {"state":0,"rdtiev":0} ],"fargostatus":{ "temperature":35.5, "volts":10.98 }}

Actual result - where did these newlines even come from?

{"relaystate":[
{"state":1,"rdtiev":0},
{"state":1,{"state":1,"rdtiev":0},
{"state":0,"rdtiev":0},
{"state":0,"rdre":44.0, "volts":10.85
}}