chore: fix drop_table_by_id fail when TableIdToName cannot found

[lichuang]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

chore: fix drop_table_by_id fail when TableIdToName cannot found

• Closes bug: fix drop_table_by_id when TableIdToName cannot found #13998

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

---

This change is 

[drmingdrmer]

Reviewed 2 of 10 files at r2, 1 of 1 files at r3, all commit messages.
Reviewable status: 3 of 10 files reviewed, 3 unresolved discussions (waiting on @lichuang)

---

src/meta/api/src/schema_api_impl.rs line 2362 at r3 (raw file):

            let db_id = dbid_tbname.db_id;
            let tbname = dbid_tbname.table_name.clone();

It looks like tbname is only used for building an error. Therefore there is no need to pass in a table_name in req. And in this scenario, the error could be UnknownTableId instead of an UnknownTable. Because when the table can not be found by (db_id, table_name), the only possible reason is that the table is remove by other transaction.

This way we do not need to be bother using table_name in req.

What say you?