Rounded date ranges with lte should set include_upper to false

[clintongormley]

As discussed in #7203 the current behaviour of lt/lte with date rounding is inconsistent. For instance, with the following docs indexed:

DELETE /t

POST /t/t/_bulk
{"index":{"_id":1}}
{"date":"2014/11/07 00:00:00"}
{"index":{"_id":2}}
{"date":"2014/11/07 01:00:00"}
{"index":{"_id":3}}
{"date":"2014/11/08 00:00:00"}
{"index":{"_id":4}}
{"date":"2014/11/08 01:00:00"}
{"index":{"_id":5}}
{"date":"2014/11/09 00:00:00"}
{"index":{"_id":6}}
{"date":"2014/11/09 01:00:00"}

This query with lt:

GET /_search?sort=date
{
  "query": {
    "range": {
      "date": {
        "lt": "2014/11/08||/d"
      }
    }
  }
}

correctly returns 2014/11/07 00:00:00 and 2014/11/07 01:00:00, but this query with lte:

GET /_search?sort=date
{
  "query": {
    "range": {
      "date": {
        "lte": "2014/11/08||/d"
      }
    }
  }
}

incorrectly returns:

• 2014/11/07 00:00:00
• 2014/11/07 01:00:00
• 2014/11/08 00:00:00
• 2014/11/08 01:00:00
• 2014/11/09 00:00:00

It should not include that last document. The lte parameter, when used with date rounding, should use ceil() to round the date up, as it does today, but include_upper should be set to false.