Tracking issue for drop database

[WenyXu]

What problem does the new feature solve?

Implement the Drop database statement and ensures resources were released correctly

• close Supports drop schema/database statement #825
• Handle potentially leaked resources #3515

What does the feature do?

• feat: implement the drop database parser #3521
• refactor: introduce the DropTableExecutor #3534
• feat: implement the drop database procedure #3541
• refactor: refactor CacheInvalidator #3550
• Support to drop metric table refactor: refactor drop table executor #3589
• Invalidate schema name key cache Invalidate schema name key cache after dropping database #3695
• Add more tests test: add tests for drop databases #3594
• Add create database procedure (for acquire locks) move create database to procedure  #3591
• Release resources correctly

Implementation challenges

No response

[sunng87]

Please make sure we do not allow cross catalog database drop by default.

[WenyXu]

Please make sure we do not allow cross catalog database drop by default.

Yes, we are under the catalog of query context by default.

[killme2008]

@WenyXu Looks like we can close this issue.

[WenyXu]

Remaining will track in #3515