Renamed contentType to resourceSubType
Link preview processing + square thumbnails.

Special handling:
 * YouTube
 * Vimeo
 * SlideShare
 * Flickr (both regular photos as sets)
Allow for a limit querystring parameter in the relatedcontent search feed.
#418 Purging the RabbitMQ queues after tests.
Merge branch 'master' into issue-413
Renamed document to collabdoc
Some more renaming to resourceSubType
Merge pull request #421 from nicolaasmatthijs/issue-413

Renamed contentType to resourceSubType
#423 follow-up

 * Moved downloadRemoteContent to oae-previews/util
 * Added testcase for downloadRemoteContent
 * Cleaned up JSDoc
 * Changed handler of how vimeo detects it can handle a url
Merge branch 'master' into preview-processor-improvements

* master: (22 commits)
  Some more renaming to resourceSubType
  Renamed document to collabdoc
  Fix broken build after 'request' module ugprade
  Adding log parameter for safe path prefix
  Updated documentation style
  Added /api/auth/shibboleth to the CSRF excempt paths
  Added test case for 418 status code
  Add 418 error code to Array of codes in oae-rest util
  Renamed contentType to resourceSubType
  iterateAll PR Follow-up: Fixed superficial styling issues.
  Added missing line break
  (CSRFReferer) Fixes from review feedback
  Google/Twitter Picture PR followup:  * Cassandra.constructUpsertQuery filters out keys with null/undefined values  * Created a TenantsUtil.getBaseUrl(tenant) utility.
  Shibboleth Authentication PR Follow up  * Using simong/passport-saml#master  * Made the SP certificate global admin only  * Added some docs  * Styling issues
  Google picture followup
  Shibboleth authentication
  Removed unneeded testcase for issue 320
  Content iterateAll fix.
  (CSRFReferer) Check referer on incoming requests to verify they are same-origin.
  Issue 320 - Ensure that a group or content item always has 1 member.
  ...
Making PP use new resourceSubType rather than contentType.
Added some documentation in default PP retriever.
Fixed regression in flickr & slideshare PPs
Follow up on square Thumbnail issues
Removed line break
Store authenticated userid on cookie, not redis

* Pro: Redis server can now have an eviction policy
* Pro: Smaller deployments can have activity and main redis together
* Pro: Cuts down one redis request per API request
* Pro: Not forced to have an absolute TTL on sessions

Con #1: UserID is visible on cookie. TODO: needs encryption

Con #2: Without absolute TTL, cookie could be hi-jacked indefinitely
(until private key changed). Only difference here between Redis impl is
that the redis cookie will expire eventually. Could attach a timestamp
to cookie and inspect refresh every so often (e.g., setting a new cookie
every 30min would require users to make a request at least every 30
seconds lest they lose their session).
Encrypting userid in cookie
Merge pull request #398 from mrvisser/cookie-session

Using cookie session instead of redis session.
Added more related items in the related unit tests.
"Cleaned up" code.
Merge branch 'related-content-limit' of git://github.com/simong/Hilary into related-content-limit