Version 0.9.4

This release has mainly focused on adding new logic, or improving existing logic without creating any breaking changes.

There is however a breaking change in the Facebook logic (the FacebookGender enum class) since I misspelled a property.

Parsing a user where gender isn't specified will no longer throw an exception (see #30 and 6100a9e).
Fixed wrong property name (typo) in the FacebookGender enum class. The property Make has now renamed to Male. This is a breaking change for anyone using this enum (see f90fc2f).

For endpoints/methods in the Instagram API that doesn't require a user context, a client ID can be specified instead of an access token. A static CreateFromClientId method has now been added to the InstagramService to better support this (see 3ce8d73).
Implemented the Search method in the Tags endpoint as suggested by @fedrch in #36 (see e84cb79).
Implemented the GetUserFeed method in the Users endpoint for getting the feed of the authenticated user (see 433dd0e).

Added Retweet and DestroyStatusMessage methods to the Statuses endpoint (see 841c7f0).
Added support for the Favorites and Lists endpoints (see ed12855).

Google allows developers to specify a server key as an alternative to access tokens. The GoogleService and GoogleOAuthClient classes have now been updated to support this (see bb27a3c).
As a common thing for the Google, Analytics and YouTube implementations, the scopes are now declared in static classes - eg. you should now use GoogleScopes.Email instead of GoogleScope.Email, and AnalyticsScopes.Readonly instead of AnalyticsScope.Readonly. The old way of accessing a scope (eg. GoogleScope.Email) has now been marked as obsolete, and will be removed entirely for v1.0 of Skybrud.Social (see 88917c9).

To have a normalized structure for the various implementations in Skybrud.Social, the Analytics implementation has now also been updated to return classes representing the entire response. This meaning that earlier a call to the API would return a class representing just the response body (JSON data) without any information about the actual HTTP request - eg. headers returned by the server.

To avoid breaking changes, the old methods for calling the API can still be used from the Analytics endpoint as before, but have been marked as obsolete. The new methods have been separated into individual Management and Data endpoints. The methods and classes now marked as obsolete will be removed entirely for v1.0 of Skybrud.Social.

Added a Tags property to the YouTubeVideoSnippet class so the tags are now properly exposed (see 14913e5).

It is a plan for the future (hopefully v1.0) to switch to Newtonsoft.Json instead of JavaScriptSerializer currently being used internally in Skybrud.Social. So to better support this move, a bunch of extension methods for JObject and JArray have now been added to the project (see 48ad1ee).