Restore exception handling for IllegalArgumentException during type resolution

[pdabre12]

Description

In #24179, the exception thrown when a parsing an unknown type was replaced from IllegalArgumentException to a new Exception UnknownTypeException. As a result of this, exception handling for IllegalArgumentException was removed. But IllegalArgumentException can be thrown at multiple places down that execution path, so this change adds exception handling for IllegalArgumentException back.

Motivation and Context

Solves the issue described in this PR: #24963

Impact

No Impact

Test Plan

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

== NO RELEASE NOTE ==

[pdabre12]

@woshizhouyihao This could resolve the internal pipeline failure you are seeing.
Unfortunately, do not have enough context on the failing query to add a unit test.

[pdabre12]

@woshizhouyihao Will you be able to try this patch in your clusters?

[woshizhouyihao]

Hi i m building a binary and deploying it. i will keep you updated

[woshizhouyihao]

I have verified those failed queries succeeded with the new build.
@amitkdutta can you approve this PR. Thanks.

[amitkdutta]

Thanks @pdabre12

[amitkdutta]

@pdabre12 @woshizhouyihao I assume with this chance, we don't need to merge the two reverts
#24963
#24961
Then we can close those 2 PR as well.