Moved all ERB processing to the outside of functions

I'm not sure if this will do anything or not, but I can't figure out why
else the email address would have been getting inserted by ERB but the
cloudmade key wouldn't be.
Merge branch 'master' of heroku.growstuff:growstuff-dev into places3
further adventures in finding the cloudmade_key
debugging output for cloudmade key (needs to be reverted later)
still trying to get cloudmade key working (should be reverted later)
do env vars show up in the js?
experimenting with tainted vars. revert this later.
experimenting with tainted vars, again. revert this later.
Use experimental user-env-compile heroku addon

It seems that heroku generally denies us access to ENV['...'] during asset
compilation. They have reasonably good reasons for this, and yet I don't
know how else we're meant to get at our API keys (other than hardcoding
them into our config files, which we don't want to do).

So, to work around this, I'm recommending the use of the (experimental,
subject to removal/change, sigh) user-env-compile heroku addon.  This
lets us use ENV during asset compilation.

For more info see
https://devcenter.heroku.com/articles/labs-user-env-compile
Merge branch 'master' of heroku.growstuff:growstuff-dev into places3
Merge branch 'master' of heroku.growstuff:growstuff-dev into dev

Conflicts:
	app/assets/javascripts/places.js.erb
removed spurious debug message from places/index
limit things-to-map to those with locations (duh)
Merge pull request #310 from Skud/final-places-fixes-really-truly

Final places fixes really truly