blast our jshint tests with our new jshintrc

We have jshintrc files now for different parts of the code. We should
pump our files through jshint as one of our tests. This shows how to do
it with the ./lib directory.
cleaned up ALL jshint warnings in lib/
fixed jshint errors throughout static
locking down jshint@0.9.1
changelog for train-2012.10.26
bump version in dev after cutting 2012.10.26
Merge pull request #2643 from seanmonstar/test-jshint-options

Add complete jshint tests
primary.js: rename 'domain' args

This renames the various "domain" parameters to avoid collision and
emphasize what exactly is meant. "fromDomain" is the domain that we're
currently fetching a .well-known/browserid file from; when we're
recursively following delegations, fromDomain is different on each loop.
"principalDomain" is constant: it is taken from the principal's email
address and remains the same for each loop.

This shouldn't change any behavior. This paves the way to split
fromDomain and principalDomain, and to pass principalDomain into each
lookup.

getWellKnown() passes its fromDomain parameter off to its callback.. I'm
not sure why (might be to avoid late-binding confusion in the delgation
case). That argument was renamed to newDomain in the closures passed
into getWellKnown(), since previously it sometimes overlapped with the
"domain" argument being passed in.
primary.ps: pass principalDomain through to everything

We now pass two arguments into each getWellKnown() and
parseWellKnownBody() call. The "fromDomain" argument changes on each
delegated lookup (it indicate which server we're fetching
.well-known/browserid from *right now*), while "principalDomain" remains
constant (and indicates which domain we really care about, regardless of
who we're currently asking about them).

This shouldn't change any behavior. It just paves the way for a later
change to add principalDomain as a query arg.
add domain= queryarg to the .well-known fetch

This should allow multiple primaries to delegate control to the same
server, by letting the server know which domain we're interested in.
This is similar to how the HTTP "Host" header enables named-based
virtual hosting. Both the Verifier and the user agent (specifically the
/wsapi/address_info handler) will add this argument. Servers which host
only one key can ignore it.

Also allow arbitrary queryargs in bin/proxy, otherwise it denies
requests with queryargs.

This should help Bigtent do dynamic .well-known lookups.
Adding vows test to demonstrate a BigTent assertion
Merge branch '2565-dynamic-wellknown-rebase2' into dev
optionally use node-cover when running npm test for backend code coverage data

To run 'PERSONA_WITH_COVER=1 npm test'.

Changes to lockdown.json are:
  rimraf@2.0.2
    -> graceful-fs@1.1.14
  cover@0.2.8
    -> underscore@1.2.4
    -> underscore.string@2.0.0
    -> cli-table@0.0.2
      -> colors@0.3.0
fix undefined check of loggedInUser

fixes #2662
update changelog after merge of fix for issue #2662 into dev

Conflicts:
	ChangeLog
	scripts/browserid.spec
update to awsbox 0.3.3
Merge pull request #2272 from jrgm/backend-code-coverage-2

optionally use node-cover when running npm test for backend code coverage data
Merge pull request #2666 from mozilla/awsupdate

update to awsbox 0.3.3

r+ Thanks @lloyd!
Merge remote-tracking branch 'origin/kapow' into dev