Observability: Adding more information to traces

Tracing information doesn't provide information related to acquiring DB locks or any other operation that Hasura performs while executing an operation, making it hard to diagnose issues like DB connections exhausted, etc. E.g. this screenshot:

### Is your proposal related to a problem?
Tracing information as currently available is not effective when trying to a subset of perf issues, especially when the DB query execution times are not a bottleneck.

### Describe the solution you'd like

Missing information is available for all major/logical operations performed by Hasura.

Start by inspecting the current tracing instrumentation and identifying which major or logical Hasura operations are represented in traces. Compare the existing trace data with the reported database-lock and connection-exhaustion diagnostic needs; the work is complete when traces expose the missing operation information, including database lock acquisition where applicable.

Written by the indexing model from the issue text.