npm_modules: Fork bower_components into Polymer 0.4.0 and 0.5.0 versions

npm_modules: Fork bower_components into Polymer 0.4.0 and 0.5.0 versions

Newly created polymer elements are only available in Polymer 0.5.0.
This change adds a Polymer 0.5.0 version of bower.json to npm_modules for
Chrome infra apps to use.
Legacy app code will still continue to be able use Polymer 0.4.0.

Summary of change (since diff is too ugly):
 - Move existing bower.json and bower_components into polymer_0.4.0 directory.
 - Copy bower.json into polymer_0.5.0 directory.
 - Update all Polymer 0.4.0 references to 0.5.0 and remove conflict
   resolution rules in polymer_0.5.0/bower.json file.
 - Run "bower update" in polymer_0.5.0.

R=agable@chromium.org

Committed: https://chromium.googlesource.com/infra/third_party/npm_modules/+/f3f825ae2d3521d889fe076bd2229f6a1fadaac6

[alancutter (OOO until 2018), 2015-01-05 02:02:19]

alancutter@chromium.org changed reviewers:
+ agable@chromium.org

[agable, 2015-01-05 20:38:26]

(Disclaimer: I don't know what I'm talking about.)

Does it work to add an additional layer of indirection in the directory
structure? From what I understand, we're going from:

appengine/third_party/npm_modules/bower_components

to

appengine/third_party/npm_modules/polymer_0.[4|5].0/bower_components

I have no idea what consequences that change will have, and what has to be done
to offset them. Maybe the bower.json changes you reference are sufficient. Just
making sure :)

[agable, 2015-01-05 20:42:19]

I see that the symlinks change in the other CL. That makes sense. LGTM.

[alancutter (OOO until 2018), 2015-01-05 22:58:34]

Committed patchset #1 (id:1) manually as
f3f825ae2d3521d889fe076bd2229f6a1fadaac6 (presubmit successful).