create es-x.x branches reflecting elasticsearch versions
create es-x.x branches reflecting elasticsearch versions

(cherry picked from commit 948a2c9)
Update to elasticsearch 2.0.0
Deprecate usage of camelCase settings

We don't want to support anymore camelCase settings in river definitions.

We deprecate in this version:

* `consumerKey`
* `consumerSecret`
* `accessToken`
* `accessTokenSecret`

Closes #57.
(cherry picked from commit 98350de)
Remove old deprecated user and password properties

We don't use anymore `user` and `password` properties since version 1.4.0. See #28.
We can now remove it from code.

Closes #58.
(cherry picked from commit f24614a)
Add oauth credentials in `elasticsearch.yml` file

We can imagine having all or part of oauth keys in `elasticsearch.yml` file instead of having them only in the river definition itself.

Twitter river definition still has precedence. But now we can for example have in elasticsearch.yml file:

```
river.twitter.oauth.consumer_key: "*** YOUR Consumer key HERE ***"
river.twitter.oauth.consumer_secret: "*** YOUR Consumer secret HERE ***"
```

Creating a river could be done like this:

```
PUT _river/my_twitter_river/_meta
{
    "type" : "twitter",
    "twitter" : {
        "oauth" : {
            "access_token" : "*** YOUR Access token HERE ***",
            "access_token_secret" : "*** YOUR Access token secret HERE ***"
        }
    }
}
```

Closes #56.
(cherry picked from commit 5439128)
Move tests to elasticsearch test framework

Closes #37.
(cherry picked from commit ffd4372)
Added user stream support

You can simply index current authenticated user timeline.

```
{
    "type" : "twitter",
    "twitter" : {
        "type" : "user"
    }
}
```

Closes #50.
(cherry picked from commit 4f13077)
Added not_analyzed to retweet user_screen_name

When the index mapping is originally created, and not_analyzed attribute value for the index property is added to make it similar to all other screen_name properties in the documents.

(cherry picked from commit 180f367)
Simplify documentation

We use SENSE examples
We don't need to specify oauth settings each time as they can be provided in `elasticsearch.yml` file.

(cherry picked from commit de0c28d)
ignore_retweets does not ignore RT

I set

```sh
curl -XPUT localhost:9200/_river/my_twitter_river/_meta -d '{
    "type" : "twitter",
    "twitter" : {
        "ignore_retweet" : true
    }
}'
```

And got this:

```
{
   "text":"RT @BrianSheehy7: Think I'll go to sleep again",
   "created_at":"2014-07-22T19:00:11.000Z",
   "source":"<a href=\"http://twitter.com/download/iphone\" rel=\"nofollow\">Twitter for iPhone</a>",
   "truncated":false,
   "language":"en",
   "mention":[
      {
         "id":1213703370,
         "name":"Brian",
         "screen_name":"BrianSheehy7",
         "start":3,
         "end":16
      }
   ],
   "retweet_count":0,
   "retweet":{
      "id":491654715126464512,
      "user_id":1213703370,
      "user_screen_name":"BrianSheehy7",
      "retweet_count":2
   },
   "hashtag":[

   ],
   "link":[

   ],
   "user":{
      "id":1104903565,
      "name":"KayBrat",
      "screen_name":"KayBrat_95",
      "location":"",
      "description":"•stay sexual•",
      "profile_image_url":"http://pbs.twimg.com/profile_images/491658775841882112/FggUrW5J_normal.jpeg",
      "profile_image_url_https":"https://pbs.twimg.com/profile_images/491658775841882112/FggUrW5J_normal.jpeg"
   }
}
```

It sounds like that setting `ignore_retweets` index actually only RT tweets!

Closes #60.

(cherry picked from commit e545309)