Add native support for range field types by using a range object

[xhaggi]

• You have read the Spring Data contribution guidelines.
• There is a ticket in the bug tracker for the project in our [issue tracker](https://github.
  com/spring-projects/spring-data-elasticsearch/issues). Add the issue number to the Closes #issue-number line below
• You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.
• You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

Closes #1862

[sothawo]

Nice work; i left a couple of comments.

What do you think about adding default range types like class IntegerRange extends Range<Integer>{}?

About the IPs - would be great to have that as well. I'll see if I find something useful

[xhaggi]

Nice work; i left a couple of comments.

Thank you, I have addressed your comments.

What do you think about adding default range types like class IntegerRange extends Range{}?

I have no strong opinion on that. Writing Range or IntegerRange makes no difference to me.

About the IPs - would be great to have that as well.

Sure, but IMO we could add it later.