Return nil lookupMapping if type conversion is not in range for lookup key

[angelamayxie]

fixes #10233

Not checking if a value is in the converted range was causing us to use incorrect keys. For example, if the literal -87840 was used as a key for a boolean/tinyint column, it would get converted to -128 and match rows with -128, even though that's not the same value.

This change checks for if a conversion is InRange, and if it's not, it returns a nil lookupMapping. The nil lookupMapping will then return false when *lookupMapping.valid() is called.

Test added in dolthub/go-mysql-server#3357

[coffeegoddd]

@angelamayxie DOLT

comparing_percentages
100.000000 to 100.000000

version	result	total
9237892	ok	5937471

version	total_tests
9237892	5937471

correctness_percentage
100.0

[coffeegoddd]

@angelamayxie DOLT

comparing_percentages
100.000000 to 100.000000

version	result	total
37519e2	ok	5937471

version	total_tests
37519e2	5937471

correctness_percentage
100.0

[zachmu]

Probably should use the same logic for this that GMS does, this seems like it was just an oversight when the latest round of bug fixes for this problem were just applied ther.

[coffeegoddd]

@angelamayxie DOLT

comparing_percentages
100.000000 to 100.000000

version	result	total
4ff5e11	ok	5937471

version	total_tests
4ff5e11	5937471

correctness_percentage
100.0

[zachmu]

LGTM!

[coffeegoddd]

@angelamayxie DOLT

comparing_percentages
100.000000 to 100.000000

version	result	total
b80ef45	ok	5937471

version	total_tests
b80ef45	5937471

correctness_percentage
100.0