Bug fixes and some Bower improvements

Bower:
- support package specifications with just a version or version range and path omitted, e.g. "package-x": "1.2.3", "package-y": "~1.2.3": the path is resolved using Bower registry based on the package name
- support "*" as a package specification, e.g. "package-x": "*": the path is resolved as above; the tag resolves to the latest stable
- support packages whose GitHub repositories have moved to a different GitHub organization (so their URL redirects from https://github.com/OldOrg/package to https://github.com/NewOrg/package)

Bower: too frequent or large bower install/update jobs would exceed the GitHub API access rate limit, locking the user out of Bower for a 1-hour timeout period
when deleting a folder from disk on Windows, CDE might delete the contents of a subfolder represented by a junction point, rather than just delete the junction itself
the editor was very sluggish on very large files with long lines (e.g. minified package sources)

Bower:
- support package specifications with just a version or version range and path omitted, e.g. "package-x": "1.2.3", "package-y": "~1.2.3": the path is resolved using Bower registry based on the package name
- support "*" as a package specification, e.g. "package-x": "*": the path is resolved as above; the tag resolves to the latest stable
- support packages whose GitHub repositories have moved to a different GitHub organization (so their URL redirects from https://github.com/OldOrg/package to https://github.com/NewOrg/package)

Bower: too frequent or large bower install/update jobs would exceed the GitHub API access rate limit, locking the user out of Bower for a 1-hour timeout period
when deleting a folder from disk on Windows, CDE might delete the contents of a subfolder represented by a junction point, rather than just delete the junction itself
the editor was very sluggish on very large files with long lines (e.g. minified package sources)

chromedeveditor