updated docs for application.getAccount()

* better document the object literal as providerOptions
* reduced usage to one example
* linked to product guide for social providers
* defined the result object as providerAccountResult
Merge pull request #92 from stormpath/docs

updated docs for application.getAccount()
it tests for custom data on all supported resources
more it tests

oh so many more to write..
tenant can have custom data, too
getCustomData vs resource.customData

getCustomData is used when you did not expand the
custom data on the parent resource

if you did expand custom data on the parent resource,
then you can use it directly from resource.customData

these tests, docs and Tenant resource change are
in reflection of that
implement application.getCustomData()
getCustomData for directory, and fix expansion issue

I observed #85 while writing the it tests for custom data
on directories, thus I’m fixing it in this commit.

The fix is to bring back the logic of “don’t cache
any requests that have query options”.  I had previously
removed this but now I’m bringing it back, as it’s simpler
than trying to write fancy query caching rules into the
datastore.

You can achieve cache warming by expanding the resource
the first time you get it, then using the getter methods
on subsequent request for the same data.
update docs
Implement ID Site logout

* add this option to createIdSiteUrl
* pass the status property on the idSiteResult
* docs
upgrade request to 2.40.0

2.41.0 appears to be having some problems with
an incorrect content length setting, and it was
breaking our it tests.

so holding back at 2.40.0 for now
write a test for the api key loader

preparing to upgrade properties-parser
upgrade properties-parser
upgrade moment, node-uuid

coverage looks good on these
updated docs for application.sendPasswordResetEmail

The API only accepts email.  Resolution for #43
fix documentation of memcached options

Port was incorrect

Now refers to “Server locations”, as it’s called in node-memcached

Refer to #73
IT tests for application.authenticateAccount()

Prove that you can authenticate an account with username or
email.

In regards to #67
IT tests for resource.customData.get()
updated docs for custom data

attempt to make the usage clearer, because it’s a bit
different if you don’t expand custom data when you request
the parent resource
typo