Rework how remoting JS compilation GYP works.

Rework how remoting JS compilation GYP works.

There was an unfortunate bug that swallowed Java stacks.
Issues were discovered when Java stacks started surfacing:
https://codereview.chromium.org/476453002/

So change the way remoting is built. It doesn't need to be
built on all bots by default: they have undefined Java versions
and likely weren't working before (and shouldn't differ).

Instead, run when run_jscompile=1 is defined in GYP:

  export GYP_DEFINES=run_jscompile=1 && build/gyp_chromium
  # or add in ~/.gyp/includes.gypi or $SRC/../chromium.gyp_env
  # or build/gyp_chromium -Drun_jscompile=1

and on the Closure Compilation Linux FYI bot:
http://build.chromium.org/p/chromium.fyi/builders/Closure%20Compilation%20Linux

This also fixes some GYP inputs problems (if I changed compile_js.gypi or
other things in remoting/ ninja wouldn't rebuild anything).

R=jamiewalch@chromium.org
BUG=none
TEST=green bots, remoting runs on Closure Compliation Linux FYI bot

Committed: https://crrev.com/b59fe188aa76f3c18a71427c5e655aa609d7c7bd
Cr-Commit-Position: refs/heads/master@{#322193}

[Dan Beam, 2015-03-25 00:47:27]

https://codereview.chromium.org/1037613002/diff/1/third_party/closure_compile...
File third_party/closure_compiler/compiled_resources.gyp (right):

https://codereview.chromium.org/1037613002/diff/1/third_party/closure_compile...
third_party/closure_compiler/compiled_resources.gyp:40:
'../../remoting/remoting_webapp_compile.gypi',
this means it'll run on the bots (see: top of file)

[Jamie, 2015-03-25 01:07:07]

lgtm

[Dan Beam, 2015-03-25 02:37:15]

The CQ bit was checked by dbeam@chromium.org

[commit-bot: I haz the power, 2015-03-25 02:38:51]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1037613002/1

[commit-bot: I haz the power, 2015-03-25 04:35:42]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-03-25 04:35:45]

Try jobs failed on following builders:
  win_chromium_x64_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[Dan Beam, 2015-03-25 17:42:41]

The CQ bit was checked by dbeam@chromium.org

[commit-bot: I haz the power, 2015-03-25 17:43:12]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1037613002/1

[commit-bot: I haz the power, 2015-03-25 18:26:00]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-03-25 18:26:54]

Patchset 1 (id:??) landed as
https://crrev.com/b59fe188aa76f3c18a71427c5e655aa609d7c7bd
Cr-Commit-Position: refs/heads/master@{#322193}

[kelvinp, 2015-03-31 23:30:53]

On 2015/03/25 18:26:54, I haz the power (commit-bot) wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/b59fe188aa76f3c18a71427c5e655aa609d7c7bd
> Cr-Commit-Position: refs/heads/master@{#322193}

Hi Dan, 

Is the closure compiler FYI bots part of CQ?
If not, doesn't mean after your change, compilation errors in remoting won't be
caught by try bots before it got landed?

Kelvin