Tracking Issue: Supports rename table

[e1ijah1]

What type of enhancement is this?

API improvement

What does the enhancement do?

As discussed in #660 , we decide to using table id as the table data path to support RENAME TABLE. This issue tracks the progress of this work.

Implementation challenges

This feature will be implemented in the following steps:

• change the table path to schema/table_id refactor(mito): change the table path to schema/table_id #728
• support renaming tables in the mito table engine, this may require to feat: implement rename table #802
  • persist the change to manifest (maybe a new MetaAction is required)
  • change the in-memory metadata
  • recover the change when reopening the table
• support renaming tables for the catalog manager in standalone mode feat: support renaming table in the catalog manger #824
  • update the catalog's metadata
• support rename table in distribute mode
• support parsing the RENAME TABLE statements in the parser and execute the rename statement feat: support parsing the RENAME TABLE statements in the parser  #780

[killme2008]

Looks like we already implement it. Thanks a lot @e1ijah1

[evenyag]

@killme2008 rename is not implemented in cluster mode, we might need to reopen this.