Ordering and filtering localized values fixes

This release fixes two bugs when querying localized content.

When specifying both an alternate locale and an order parameter with no locale path segement (e.g. fields.startTime instead of fields.startTime.fr-CA), the entries were ordered ordered by default value instead of the localized value.

A similar issue could be triggered when filtering using a deep path (e.g. fields.channels.sys.id) and an alternate locale.

Both query operators now respect the locale defined by the locale parameter when applying the filter or order.