[SPARK-29526][SQL] UNCACHE TABLE should look up catalog/table like v2 commands

[imback82]

What changes were proposed in this pull request?

Add UncacheTableStatement and make UNCACHE TABLE go through the same catalog/table resolution framework of v2 commands.

Why are the changes needed?

It's important to make all the commands have the same table resolution behavior, to avoid confusing end-users. e.g.

USE my_catalog
DESC t // success and describe the table t from my_catalog
UNCACHE TABLE t // report table not found as there is no table t in the session catalog

Does this PR introduce any user-facing change?

yes. When running UNCACHE TABLE, Spark fails the command if the current catalog is set to a v2 catalog, or the table name specified a v2 catalog.

How was this patch tested?

New unit tests

[imback82]

cc: @cloud-fan / @viirya / @rdblue

[imback82]

@viirya When #26179 is merged, I can rearrange the code so that cache/uncache go together.

[SparkQA]

Test build #112576 has finished for PR 26237 at commit 9f234e9.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds the following public classes (experimental):
• case class UncacheTableStatement(

[SparkQA]

Test build #112608 has finished for PR 26237 at commit 7481684.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[dongjoon-hyun]

LGTM. (I left two minor comments, @imback82 ).

[dongjoon-hyun]

Thank you, @imback82 , @cloud-fan , @viirya .

The last commit is only comment and test case name changes in DDLParserSuite. For DDLParserSuite, I manually ran the test again.

Merged to master.

[imback82]

Thanks everyone!

[SparkQA]

Test build #112625 has finished for PR 26237 at commit 53448b2.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.