[Improvement] Improve catalog interface

[ChaomingZhangCN]

Search before asking

• I searched in the issues and found nothing similar.

Motivation

Catalog api differences between Java and Cpp.

Operation	Java Support	C++ Support
Catalog
Options	✅	❌
CaseSensitive	✅	❌
Database
CreateDatabase	✅	✅
ListDatabases	✅	✅
GetDatabase	✅	❌
DropDatabase	✅	❌
AlterDatabase	✅	❌
Table
CreateTable	✅	✅
ListTables	✅	✅
GetTable	✅	❌
DropTable	✅	❌
RenameTable	✅	❌
AlterTable	✅	❌
View
CreateView	✅	❌
ListViews	✅	❌
GetView	✅	❌
DropView	✅	❌
AlterView	✅	❌
Partition
CreatePartition	✅	❌
ListPartitions	✅	❌
DropPartition	✅	❌
Tools/Helper (C++)
DatabaseExists	✅（GetDatabase）	✅
TableExists	✅（GetTable）	✅
GetDatabaseLocation	✅（Warehouse）	✅
GetTableLocation	✅（GetTable）	✅
LoadTableSchema	✅（GetTable）	✅

I propose that adding missing methods for c++ and marking the methods in tools/helper scope deprecated in c++.
The standard api name should follow Operation-Object form, like CreateTable.

This issue should be resolved before introducing rest catalog.

Solution

No response

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!

[lxy-9602]

Great work! It aligns well with the Java catalog interface design. We may consider introducing a Table class in paimon-cpp which serves as a central abstraction for accessing metadata (e.g., schema, location).