Fix delayed expansion issue while setting MEM_OPTS

Because delayed expansion is not used during a for loop, MEM_OPTS is never set which is leading to issues with people compiling scala during a first_run of activator (Error during sbt execution: java.lang.OutOfMemoryError: PermGen space is being thrown).

This properly sets the variables used so the options are passed along okay.
Merge pull request #539 from lespea/patch-1

Fix delayed expansion issue while setting MEM_OPTS
Sets the ping time to 25s to make Activator work with IE11
Merge pull request #542 from typesafehub/wip/h3nke-ie-timeout

Sets the ping time to 25s to make Activator work with IE11
Fix annoying random behaviour on header
Merge pull request #546 from typesafehub/fix/header

Fix annoying random behaviour on header
Fix the ugly white bg in code
Merge pull request #547 from typesafehub/wip/fix-code

Fix the ugly white bg in code
Fix spelling of successful in run.html
Fix spelling of successful in test.html
Ask for reset when a localstorage value is suspect
Use automatic scala version in launcher properties

This is intended to fix #534 where if we try to launch
an older version of activator we give it the too-new
Scala; it would also in theory fix a future problem
where if we try to launch a newer-than-us activator on
a newer scala things wouldn't work.

My only misgiving is that I guess there's some reason we didn't
do this before (some reason we hardcoded the scala version before)
but I guess we will find out.
Merge pull request #569 from typesafehub/wip/havocp-auto-scala

Use automatic scala version in launcher properties
Only prints instructions upon successful cloning of template.
Merge pull request #568 from typesafehub/wip/h3nk3-improved-instructions

Wip/h3nk3 improved instructions
Fixes embarrassing compilation error
Merge pull request #570 from typesafehub/wip/h3nk3-compilation-error-fix

Fixes embarrassing compilation error
When copying script/launchjar to new project, use old launch jar

Activator home may not match our own version, so we glob the
launch jar if we have to (first checking for an exact match,
just for efficiency and in case there are multiple).

Fixes #555
Don't copy scripts to new project without a launchjar

If for some reason we can't find the launch jar, don't
copy the scripts, since they won't work by themselves.
Merge pull request #571 from typesafehub/wip/havocp-clone-old-launcher

Fix cloning launch jar from old activator home