Adding support for all_key_match

[jainavi17]

Returns whether all keys of a map match the given predicate. Returns true if all the keys match the predicate (a special case is when the map is empty); false if one or more keys don’t match; NULL if the predicate function returns NULL for one or more keys and true for all other keys.
Test plan

Added unit tests.
Build successfully using the following terminal command

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

== RELEASE NOTES ==

General Changes

• Add support for ALL_KEYS_MATCH udf in Presto

  • Returns whether all keys of a map match the given predicate. Returns true if all the keys match the predicate (a special case is when the map is empty); false if one or more keys don’t match; NULL if the predicate function returns NULL for one or more keys and true for all other keys.
  • SELECT ALL_KEYS_MATCH(map(ARRAY['a', 'b', 'c'], ARRAY[1, 2, 3]), x -> length(x) = 1); -- true

[jainavi17]

@feilong-liu If you could review the diff.

[feilong-liu]

Nit, remove the "::" at the end of the release note description.

[wanglinsong]

Please update release notes base on the guidelines: https://github.com/prestodb/presto/wiki/Release-Notes-Guidelines#phrasing

for example

== RELEASE NOTES ==
General Changes

• item 1 ...

[rschlussel]

Also, the commit message should follow the guidelines in the blog linked here: https://github.com/prestodb/presto/wiki/Review-and-Commit-guidelines#commit-formatting-and-pull-requests. So, the commit message title should be "Add support for all_keys_match function" (rather than "Adding"). And then the body can have a brief description.