[AMORO-3065] Optimizing rest api efficiency for table detail

[klion26]

Why are the changes needed?

Close #3065.

Brief change log

For table detail we'll retrive detail info from underlying table, before the change there will be two call to the catalog when loading the table: 1) check whether the database exists, 2) load the table for the detail info. After the change, the first call to catalog has been removed, and use the second call to check if the table exists.

How was this patch tested?

• [ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

• [ ] Add screenshots for manual tests if appropriate

• [ ] Run test locally before making a pull request

Documentation

• Does this pull request introduce a new feature? (no)
• If yes, how is the feature documented? (not applicable)

[klion26]

@zhoujinsong @majin1102 could you please have a look when you're free, thanks.

[zhoujinsong]

Thanks for the work! @klion26

[klion26]

@baiyangtx @zhoujinsong thanks for the review and merging!