Attempt to simplify the cluster configuration.

Since RFC-1738 we have a well defined and standard way to define URI.

Reason why I tried to configure my elasticsearch like so:

    elasticsearch.Elasticsearch([
        'https://admin:password@1.elasticsearch.cloud.com',
        'https://admin:password@2.elasticsearch.cloud.com',
        'http://3.elasticsearch.lan:9200'
    ])

Today the alternative is to write something like:

    elasticsearch.Elasticsearch([
        {'host': '1.elasticsearch.cloud.com', 'port': 443, 'use_ssl': True, 'http_auth': 'admin:password'},
        {'host': '2.elasticsearch.cloud.com', 'port': 443, 'use_ssl': True, 'http_auth': 'admin:password'},
        '3.elasticsearch.lan:9200'
    ])

Do you think it may be interesting to add this way to defined it on a standard way?
The main reason I am asking is that URI are easier to define in a .dot ini file.

I started to add it directly to the project which is using elasticsearch-py[0] but we though it could be better to have it directly here.

Any thoughts?

[0] https://github.com/spiral-project/daybed/pull/267#issuecomment-62804246
no - then it is at the discretion of the `connection_class` - http is default but it could be different. Providing `//` instead of `http://` will make the scheme part of the parsed result empty so we will know that no explicit scheme has been requested (and might therefore potentially conflict with the choice made by the `connection_class`).