Consolidate JS dependency install with npm

See http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbs/lp1680624_bower_to_npm for a first stab at this. Tests pass, and there appear to be no regressions in the handful of staff client interfaces I've tried to date.

Force-pushed the branch to incorporate changes that had been left in the middle of a rebase to add the bug prefix (jeez).

Allow me to offer a regression test that will hopefully prevent these from showing up in the future!

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbs/lp1680312_test_sql_gettext

Ugh, wrong browser tab, wrong bug for that regression test.

Sign-offs for Dan's 2 NPM commits pushed:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/berick/lp1680624-bower-to-npm-signoff

I removed the installed build directory and local bower/node files, re-ran "npm install" to fetch the deps. Tests passed. Copied build directory into place and various web staff UI's behaved as expected.

I didn't merge to master, thinking it might be good to test the branch on a fresh install, which I have not done.

Noted by Ben Shum in IRC, we should also remove the bower install bits from the various installer makefiles.

Excellent point! I shall work on removing those remaining bits.

And I have, with a new branch at http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbs/lp1680624-bower-to-npm that includes Bill's signoffs on the first two commits and a follow-up with the bower package install and release building bits.

I *think* that's it!

Aside: at some point in the 3.0 cycle we should remove the file-saver and sortable directories in Open-ILS/web/js and just use npm to pull those in, too.

Test install from scratch worked for me, working web client too. Picked everything to master, cool stuff!