docs: Move rich logging documentation to README.md

[juanmichelini]

Summary

Moves the rich logging documentation from a separate benchmarks/utils/logging.md file into the main README.md as a new section.

Motivation

Addresses review feedback from @simonrosenberg on PR #413, who asked:

Does this require its own md file? Or should it be a section of the README.md?

Consolidating the documentation in the README makes it:

• More discoverable for users
• Easier to maintain (single source of truth)
• Consistent with how other feature documentation is organized in the project

Changes

• ✅ Added "Rich Logging" section to README.md after "Running Benchmarks"
• ✅ Removed benchmarks/utils/logging.md
• ✅ No changes to functionality, only documentation organization

Related

• Addresses: (feat)Rich logging #413 (comment)
• Original PR: (feat)Rich logging #413

[simonrosenberg]

@OpenHands read the PR diff. The new section in the README.md is very long. Make it shorter, only share the essential info

[openhands-ai]

I'm on it! simonrosenberg can track my progress at all-hands.dev

[openhands-ai]

Summary

I addressed the PR review feedback requesting to shorten the Rich Logging section in README.md.

Checklist

✅ Read the PR diff - Reviewed the full Rich Logging section that was added (lines 120-221, ~100 lines)
✅ Made it shorter - Condensed from ~100 lines to ~18 lines
✅ Kept only essential info - Retained:

• How to enable (RICH_LOGGING=1)
• How to disable colors (NO_COLOR=1)
• Brief example of output format
• Note that file logging is unaffected
  ✅ Removed non-essential details:
• Detailed explanations of 5 different log types
• Full summary fields table (9 rows)
• Color coding explanation
• Verbose file logging section
  ✅ Changes are concise - Only modified the Rich Logging section, no extraneous changes
  ✅ Pushed to remote - Commit d2d8a27 pushed to move-logging-docs-to-readme branch

Result

The Rich Logging section now provides a quick reference for users to enable the feature and understand the output format, without overwhelming documentation that could live elsewhere if detailed reference is needed later.