Wrong field types in indexes

[BagritsevichStepan]

Describe the bug
If the field type in the document and in the index differ, we should not return this document in FT.SEARCH or FT.AGGREGATE.

For example:
Initialize:

127.0.0.1:6379> HSET h1 even true value one
(integer) 2
127.0.0.1:6379> HSET h2 even false value 1
(integer) 2
127.0.0.1:6379> FT.CREATE i1 on HASH SCHEMA value NUMERIC SORTABLE
OK

Redis:

127.0.0.1:6379> FT.SEARCH i1 "*"
1) (integer) 1
2) "h2"
3) 1) "even"
   2) "false"
   3) "value"
   4) "1"

Dragonfly:

127.0.0.1:6379> FT.SEARCH i1 "*"
1) (integer) 2
2) "h2"
3) 1) "value"
   2) "1"
   3) "even"
   4) "false"
4) "h1" // Wrong. We should not return this document
5) 1) "value"
   2) "0"
   3) "even"
   4) "true"

At the same time, if the field is missing in the document, we should return this document. For example:

Redis:

127.0.0.1:6379> HSET h1 even true
(integer) 1
127.0.0.1:6379> HSET h2 even false value 1
(integer) 2
127.0.0.1:6379> FT.CREATE i1 on HASH SCHEMA value NUMERIC SORTABLE
OK
127.0.0.1:6379> FT.SEARCH i1 "*"
1) (integer) 2
2) "h2"
3) 1) "even"
   2) "false"
   3) "value"
   4) "1"
4) "h1"
5) 1) "even"
   2) "true"