Make worker not fail on getOptionalCatalogMetadata during coercion resolution

[weijiii]

Description

• To address SQL path in session causes worker nodes to fail when resolving functions #17598
• As discussed on slack, fix this from NoOpTransactionManager

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:

[weijiii]

@raunaqmorarka @martint Could you guys also take a look at this? This was from a discussion with Dain and we want to move along with it. Thanks!

To briefly sum it up, when resolving coercion for complex types, FunctionResolver#resolveCoercion may be called recursively. In the midst of that there is could be a (nested) coercion that cannot be resolved using all candidates from the system function namespace. This was fine before because the exception would be smothered in SignatureBinder#canCast, but with the presence of SQL path this would throw UnsupportedOperationException instead.

[github-actions]

This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua

[mosabua]

@dain @martint could you chime in here .. you were part of the discussion on slack

[github-actions]

This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua

[github-actions]

Closing this pull request, as it has been stale for six weeks. Feel free to re-open at any time.

[mosabua]

I discussed this with @martint and @dain and this is most likely is not an issue anymore. Please retest and if necessary reopen this PR;