Make client interfaces consistent with property name plurality

[haacked]

What?!

Here's IGitHubClient

public interface IGitHubClient
{
    IConnection Connection { get; }

    IAuthorizationsClient Authorization { get; }
    IAutoCompleteClient AutoComplete { get; }
    IOrganizationsClient Organization { get; }
    IRepositoriesClient Repository { get; }
    IReleasesClient Releases { get; }
    ISshKeysClient SshKey { get; }
    IUsersClient User { get; }
}

Here's IObservableGitHubClient

public interface IObservableGitHubClient
{
    IObservableAuthorizationsClient Authorization { get; }
    IObservableAutoCompleteClient AutoComplete { get; }
    IObservableOrganizationsClient Organization { get; }
    IObservableRepositoriesClient Repositories { get; }
    IObservableSshKeysClient SshKey { get; }
    IObservableUsersClient User { get; }
}

Notice the inconsistencies. All the property names are singular except for Releases. The observable interfaces is missing the Releases property and it has a Repositories property instead of Repository.

I chose singular property names so they map more or less to entities.

For example, here are ways you might interact with a repository:

githubClient.Repository.Get("owner", "name");
githubClient.Repository.GetAllForCurrent();

We should make sure it's all consistent, but I wanted to get some feedback first.

1. Do you like the singular property name approach? Or would you prefer plural?

[haacked]

@half-ogre got an opinion on this?

[half-ogre]

@haacked: For now, I like going singular. I had another approach in mind, as well, but I need to think on it a bit more and poke around before I pitch it.

[haacked]

I did this in 9a33c68