Adding support for NO_KEYS_MATCH udf in presto

[jainavi17]

Test plan

Added unit tests.
Build successfully using the following terminal command

• ./mvnw clean install -Dtest=TestNoKeysMatchFunction -fn -pl presto-main

== RELEASE NOTES ==

General Changes
- Add function :func:`no_keys_match`

[feilong-liu]

Refer to #19853 (review) for similar comments

[pranjalssh]

Please address Rebecca's comments from other PR and do same for all PRs. Also make sure all required jobs are passing

[jainavi17]

Please address Rebecca's comments from other PR and do same for all PRs. Also make sure all required jobs are passing

Hi @pranjalssh thanks for your comment. Its address now. Please have a look.

[rschlussel]

can you rename the function no_keys_match (or alternatively no_key_matches is fine too)?

[kaikalur]

can you rename the function no_keys_match (or alternatively no_key_matches is fine too)?

I think keeping them consistent with the array ones (NONE_MATCH etc) is ok. But I'm ok with rename as well.

[rschlussel]

can you rename the function no_keys_match (or alternatively no_key_matches is fine too)?

I think keeping them consistent with the array ones (NONE_MATCH etc) is ok. But I'm ok with rename as well.

I'd rather change, as NONE_KEY_MATCH is harder to parse/understand. We can keep internally for these functions though, so:
all_keys_match
no_keys_match
any_keys_match

[jainavi17]

can you rename the function no_keys_match (or alternatively no_key_matches is fine too)?

I'm trying to keep the name same as array function so that its easier to find. We have NONE_MATCH in array. Let me know your thoughts.