Fixes #9049

A numeric range filter with float values behaves inconsistent when having an integer index. A range filter with gte: 1.5 would still match a value of 1.

Note this only affects filters when an integer index is created. If having a float index, or having no index at all, behavior is sound.

This adds a test to assert behavior. I've added a function for converting a float range into an integer range respecting integer bounds.

All Submissions:

• My PR targets the dev branch (not master) and my branch was created from dev.
• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?