Do not wrap with Slice for comparisons and hashing

[wendigo]

Description

Saves on the allocation while comparing

Additional context and related issues

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

## Section
* Fix some things. ({issue}`issuenumber`)

[pettyjamesm]

LGTM, once the length vs toIndex fix is made

[starburstdata-automation]

Started benchmark workflow for this PR with test type = iceberg/sf1000_parquet_unpart.

Building Trino finished with status: success
Benchmark finished with status: success
Comparing results to the static baseline values, follow above workflow link for more details/logs.
Status message: NO Regression found.
Benchmark Comparison to the closest run from Master: Report

[pettyjamesm]

Will be interested to see if this yields a perf difference in benchmarks, but I kind of doubt it. The slice allocation and equals method may have been inlined before yielding essentially similar code. It shouldn't hurt though, so no objections to the change as is even without a measurable lift.

[wendigo]

@pettyjamesm I doubt that but worth checking anyway :)