log internal table name also if any error with respect to a certain table id occurs

[lmatz]

For example, error like this:

mem-table operation inconsistent! table_id: 1190,

Suggested by @MrCroxx

Although we can find table ID to table name mapping on the Grafana,

for on-prem users, it would be more convenient if the user could post the log to us to investigate. It is also likely that he may not deploy the monitoring stack or the monitoring stack can go wrong due to unknown reasons.

[BugenZhao]

The best approach is to always enter a tracing::Span that provides fields like table_id whenever we perform table operations. However, #12959 (comment) told us that frequent span construction will lead to performance problems.

I will try doing some exploration on this. Otherwise we may attach such context manually.