feat: consume read/write metrics in execution timeline and resource p…

[amankoli09]

Closes #298

Description

This PR addresses the missing storage metrics in the ExecutionTimeline and ResourceProfile trace UI components. While the type definitions for read_bytes, read_limit, write_bytes, and write_limit were already available in the hooks, the frontend interface lacked the implementation to actually warn developers about limits for these storage variables.

Changes Made

• ResourceProfile: Updated the component to consume the memory and storage IO limit metrics. It now renders visual warning indicators when any of these storage/memory metrics approach the 90% threshold.
• ExecutionTimeline: Updated to optionally accept resourceProfile as a prop. It now displays a clear storage IO warning banner on the execution timeline when read_bytes or write_bytes approach the limits.
• Trace Page: Passed trace.resource_profile to the ExecutionTimeline component in the trace page.tsx.

These changes give developers full visibility into both compute and storage bottlenecks, providing an early warning system before their contracts fail in production due to storage exhaustion issues (e.g., out of gas or LimitExceeded failure).