src: update `lodash-amd` require paths

This way is compatible with the way npm installs the `lodash-amd`
package by default. Otherwise we would need to do some symlink
hackery, which we would like to avoid.
Plumbing: change "lodash-modern" to "lodash-amd"

Matches the way that npm would install the `lodash-amd` module.
package: add "main" and "dependencies" fields
package: add "browserify.transform" field

Since `scribe` is written using AMD module syntax, the `deamdify`
transform can be used to make it compatible with `browserify`.

Depends on: https://github.com/lodash/lodash-amd/pull/2
package: add "version" field to package.json

Otherwise npm has problems installing it from a git repo / tarball
package: use ~ for lodash-amd instead of ^

Better older npm support.
package: add "repository" field

Fixes npm's warning:

    npm WARN package.json scribe@0.1.10 No repository field.
package: remove "browserify" section

Instead, let's document that users will need to use the
`--global-transform=deamdify` option when compiling via browserify.

That is a lot easier than forking and patching all of scribe and
its plugins and dependencies in order to add these 3 silly lines.
example: update "lodash-amd" require path

Matches the changes in 87cee029074bf3a594637f3a48cb2138c2b181e8.
test: update "lodash-amd" require path

Matches the changes in 87cee029074bf3a594637f3a48cb2138c2b181e8.
term-project: update "lodash-amd" require path

Matches the changes in 87cee029074bf3a594637f3a48cb2138c2b181e8.
Merge pull request #175 from Automattic/add/browserify-support

Add "browserify" support