global: investigate upgrade of JavaScript dependencies

[GraemeWatt]

Pinned versions of JavaScript packages have mostly been unchanged in the history of the project over ~10 years. It should be investigated whether these versions can be upgraded.

hepdata/hepdata/modules/dashboard/webpack.py

Lines 39 to 43 in ab06dbc

	"crossfilter2": "~1.4.0",
	"d3": "~3.5.12",
	"d3-tip": "~0.6.7",
	"dc": "~2.0.0",
	"typeahead.js": "0.11.1"

hepdata/hepdata/modules/records/webpack.py

Lines 46 to 48 in ab06dbc

	"clipboard": "~1.5.5",
	"d3": "~3.5.12",
	"d3-tip": "~0.6.7"

hepdata/hepdata/modules/search/webpack.py

Lines 29 to 31 in ab06dbc

	"d3": "~3.5.12",
	"d3-tip": "~0.6.7",
	"typeahead.js": "0.11.1"

hepdata/hepdata/modules/theme/webpack.py

Lines 47 to 51 in ab06dbc

	"bootstrap-sass": "~3.3.5",
	"bootstrap": "~3.3.5",
	"font-awesome": "~4.6.3",
	"toastr": "~2.1.2",
	"semantic-ui-less": "~2.5.0"

See also issue #210 to upgrade font-awesome. Investigating breaking changes is not straightforward because the JavaScript code is not tested directly (#156), only indirectly via the end-to-end tests.