Avoid getFunctionMetadata for connector provided functions

[weijiii]

I am trying to use SQL path in production and have bumped into some issues. At the moment we only need to support scalar functions via this way so I did not look into the parts where getAggregationFunctionMetadata is used. The changes in this PR may not align with the community's plan to resolve them but I would like to collect some thoughts so that we can move along with it internally for the short term. Thanks.

Description

• Using catalog provided functions with SQL paths in the session causes query fail on worker node on code paths involving operations not allowed on workers
• deterministic is included in ResolvedFunction but not used in ExpressionOptimizer and ExpressionInterpreter. Instead we make other method calls to get function metadata.
• Similar to deterministic I think we can carry deprecated in ResolvedFunction, and description only when the function is deprecated, so for most cases the size of the corresponding QualifiedName object would not increase much.
• Related to Make worker not fail on getOptionalCatalogMetadata during coercion resolution #17644

Release notes

(x) This is not user-visible or 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:

[hashhar]

cc: @dain @martint

[raunaqmorarka]

@weijiii please rebase this one to master

[weijiii]

@raunaqmorarka Rebased. Thanks.

[weijiii]

Sync'ed offline with Martin; deprecation and description is not in the purpose of ResolvedFunction; instead we should be able to short-circuit the deprecation check when in worker's context, or better to find why worker is re-analyzing function nodes for types

[dain]

@weijiii given the comment above, should this PR be closed?

[dain]

@weijiii I created a different patch that I think works around this issue. If it doesn't fix it for you, let me know