Introduce getSqlInvokedFunctions SPI and BuiltInPluginFunctionNamespaceManager for registering sql invoked functions

[pdabre12]

Description

Introduces a new getSqlInvokedFunctions SPI in Presto, which only supports SQL invoked functions. This SPI enables plugins to register SQL invoked functions via a new built-in plugin function namespace manager interface: BuiltInPluginFunctionNamespaceManager.

Motivation and Context

This change is motivated by the need to safely support SQL invoked functions that may overlap with native C++ functions
pulled from the sidecar. By registering inlined SQL invoked functions through a dedicated SPI and validating them against the functions residing in the default function namespace manager, we ensure clear separate and prevent conflicts in function resolution.

Impact

No impact for now, but after this change the inlined SQL invoked functions would no longer be registered as built in functions under the BuiltInTypeAndFunctionNamespaceManager but instead be provided via a plugin.

Test Plan

CI and Unit tests

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

SPI changes
* Add a new  `getSqlInvokedFunctions` SPI  in Presto, which only supports SQL invoked functions

General Changes
* Add a new built-in plugin function namespace manager interface: `BuiltInPluginFunctionNamespaceManager`.

[pdabre12]

@rschlussel @tdcmeehan Can you please have a look?

[kevintang2022]

Hi Pratik. I have some questions:

1. Why are we only doing this for SqlInvoked function? Is it just for the inline sql functions use case?
2. What happens if there is a naming conflict? The server fails to start. Do you think it would be useful in the case that we do run into a conflict, then we have some logic to determine which of the two functions to keep?