fix: Redesign request log in response metadata menu

[sub-hub]

PR Checklist

• Required Checks
  • Have you added type definitions?
  • Have you tested your changes?
  • Have you checked that it won't break any existing features?
• If your PR uses models¹, check the following:
  • Have you checked if it works normally in all models?
  • Have you checked if it works normally in all web, local, and node-hosted versions? If it doesn't, have you blocked it in those versions?
• If your PR is highly AI generated², check the following:
  • Have you understood what the code does?
  • Have you cleaned up any unnecessary or redundant code?
  • Is it not a huge change?
    • We currently do not accept highly AI generated PRs that are large changes.

Summary

It's currently very inconvenient to view request responses in the request logs within the metadata window.
This is because the response is located below the body, requiring a lot of scrolling to see it.

I solved this issue with a very simple fix using details and summary tags, allowing users to open only the parts they want to see without increasing complexity.

Additionally, since this window was using hardcoded text colors, I modified it to use textcolor instead.

Footnotes

1. Modifies the behavior of prompting, requesting, or handling responses from AI models. ↩

2. Over 80% of the code is AI generated. ↩

[cubicj]

Verified the request log display path. Seeing this PR made me realize how inconvenient the always-expanded request body was, and the collapsible body/response sections solve that neatly without changing the underlying fetch log data path.

Check, tests, and build pass locally.

Approving — thanks for the contribution!