fix: Allow companion functions when result type is not resolvable given intermediate type

[rui-mo]

The registrations of partial and merge companion functions does not require the
result type is resolvable given intermediate type. This PR removes the
limitations for them.The registration of merge_extract companion function used
to depend on the resolving, and this PR uses the passed-in result type rather
than the resolved from intermediate type.

[netlify]

✅ Deploy Preview for meta-velox canceled.

Name	Link
🔨 Latest commit	3d2f9e5
🔍 Latest deploy log	https://app.netlify.com/sites/meta-velox/deploys/677f42032b1ccf0008a6a673

[zhztheplayer]

@rui-mo Thank you for taking this on. I remember we needed to bypass this check as well to make the decimal aggregate functions work. Or we don't need that change anymore?

[rui-mo]

@zhztheplayer Thanks for the pointer! In Gluten we expect that all the names will end with "_merge_extract," however according to this reasoning, the names may have other suffixes. For instance, we would obtain the names for sum and average as follows. I'll investigate further to see how to incorporate this section with Gluten.

avg_merge_extract_DECIMAL, avg_merge_extract_double
sum_merge_extract_bigint, sum_merge_extract_DECIMAL, sum_merge_extract_double

[zhztheplayer]

@zhztheplayer Thanks for the pointer! In Gluten we expect that all the names will end with "_merge_extract," however according to this reasoning, the names may have other suffixes. For instance, we would obtain the names for sum and average as follows. I'll investigate further to see how to incorporate this section with Gluten.

avg_merge_extract_DECIMAL, avg_merge_extract_double
sum_merge_extract_bigint, sum_merge_extract_DECIMAL, sum_merge_extract_double

Sounds reasonable. Look forward to a solution here. Thanks!