Add Bower Support

[Scott González]

bower install jquery-ui should install the individual source files with @VERSION replaced. Bower users will be expected to handle minification and concatenation on their own. This should be easily accomplies with the addition of AMD (#9464).

When this is ready, we'll need to claim ownership of the jquery-ui component in the Bower registry: ​https://github.com/bower/bower/issues/120

We decided to keep the "jqueryui" package as-is, instead of trying to take it over. That avoids various problems with backwards compatibility for existing bower users.

[Jörn Zaefferer]

Not super useful without AMD support, so moving this as well.

[tj.vantoll]

I looked into this a bit. This is more or less the bower.json we need (minus the dev dependencies, which are covered by #9507):

{
	"name": "jquery-ui",
	"version": "1.11.0pre",
	"ignore": [
		"**/.*",
		"build",
		"demos",
		"dist",
		"external",
		"tests"
	],
	"dependencies": {
		"jquery": ">=1.6"
	}
}

Other than the version, I'm not sure how much value there is in generating this file. The name will almost certainly never change, and we don't have a list of ignorable files, or our jQuery core version dependency stored anywhere currently.

[Scott González]

We do have the jQuery core dependency listed ​in a grunt task. We should either move that to a separate file and populate both from that or just have the manifest pull the version out of bower.json. Once we start using Bower, I'm ok with treating it as a canonical source for information that doesn't belong on package.json.

[tj.vantoll]

PR: ​https://github.com/jquery/jquery-ui/pull/1189

[TJ VanToll]

All: Add Bower support

Fixes #9465 Closes gh-1189

Changeset: e837d11d6b3c8517e322ded24faaa400443402ef