Merge pull request #3 from special/master

[telepathy-sasl-signon] Set CredentialsNeedUpdate flag after failed login
[telepathy-sasl-signon] Build Facebook authentication responses without libsoup

libsoup would escape parameters too much, resulting in authentication
failures with some recent server-side changes by Facebook. The response
string is simple to build and escaping is unnecessary for all feasible
inputs.
Merge pull request #4 from special/no-soup

[telepathy-sasl-signon] Build Facebook authentication responses without libsoup
[telepathy-sasl-signon] Use default_credentials_username for fallback

Display name is meant to be user-visible and user-modifiable, it's not
suitable for using as a login name. We store
default_credentials_username for that purpose instead.
Merge pull request #5 from special/default-username

[telepathy-sasl-signon] Use default_credentials_username for fallback
[telepathy-sasl-signon] Include ClientSecret in signon requests if defined

Fixes signon with some services (e.g. google) that require ClientSecret
for refreshing tokens.
Merge pull request #6 from special/google-refresh

[telepathy-sasl-signon] Include ClientSecret in signon requests if defined
[mcp-account-manager] Use service name and account ID for telepathy account name

The traditional account names generated with the username don't fit us
well, especially since the username often isn't actually available when
creating an account. Also, they can be reused for different accounts
after being deleted.

We can use the service name and the account ID to generate a telepathy
account name instead, which is properly unique and reproducible. This
same technique is used by other account managers, such as GOA.
Merge pull request #7 from special/account-names

[mcp-account-manager] Use service name and account ID for telepathy account name
[mcp-accout-manager] Use provider icon instead of service icon