Allow specifying optional parameters to pass to the Authorization token URL.

Allow specifying optional parameters to pass to the Authorization token URL.
 * For an example of such parameters, see http://code.google.com/apis/accounts/docs/OAuth_ref.html#GetAuth
 * Updates all samples which use the chrome_ex_oauth.js library to the most recent code.
 * Bumps the versions of all samples which got an updated OAuth library.

BUG=None
TEST=None

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=54841

[kurrik.chromium, 2010-07-15 22:37:21]

I'm updating the OAuth library to support optional Google parameters in the
Authorization token URL.  These changes are reflected in:

chrome/common/extensions/docs/examples/extensions/oauth_contacts/chrome_ex_oauth.js

I also realized that there were 3 samples which used the library and they were
getting out of sync, so I updated the code on all of them to the most up to date
library and bumped the version numbers in the manifest files.

[Aaron Boodman, 2010-08-02 21:32:52]

Shame that the library code is copied that way, but I can't think of a
workaround.

LGTM

[kurrik.chromium, 2010-08-03 23:36:56]

I was pretty unhappy about this too.  Do you think we could move the library to
another project and do something with svn:externals?  Or would it be possible to
move the library into a central location and use symlinks? I'm not really sure
what the standard practices are in this kind of situation.

On 2010/08/02 21:32:52, Aaron Boodman wrote:
> Shame that the library code is copied that way, but I can't think of a
> workaround.
> 
> LGTM