[EPIC] Improve `metrics` tracking in `EXPLAIN ANALYZE`

### Is your feature request related to a problem or challenge?

This issue is to track ideas for improving metrics tracking, such as implementing useful metrics that are currently missing.

- [x] https://github.com/apache/datafusion/issues/16244
- [ ] https://github.com/apache/datafusion/issues/16619
- [ ] https://github.com/apache/datafusion/issues/16904
- [ ] https://github.com/apache/datafusion/issues/16945
- [x] https://github.com/apache/datafusion/issues/17027
- [ ] https://github.com/apache/datafusion/issues/18116
- [ ] https://github.com/apache/datafusion/issues/18195
- [ ] https://github.com/apache/datafusion/issues/18218
- [x] https://github.com/apache/datafusion/pull/18406
- [x] https://github.com/apache/datafusion/issues/18410
- [x] https://github.com/apache/datafusion/issues/18409
- [x] https://github.com/apache/datafusion/issues/18407
- [ ] https://github.com/apache/datafusion/issues/18456
- [x] https://github.com/apache/datafusion/issues/18689
- [x] https://github.com/apache/datafusion/issues/18795
- [x] https://github.com/apache/datafusion/pull/18577

### Describe the solution you'd like

_No response_

### Describe alternatives you've considered

_No response_

### Additional context

_No response_

Start by reviewing the linked child issues and pull requests to understand which metrics have already been addressed and which remain open. Choose a specific outstanding item before locating its implementation and tests; this epic is complete only when the selected missing metrics work is implemented and verified.

Written by the indexing model from the issue text.