feat: Surface event scheduling in the dashboard (#4720)

## Description

- Users can schedule events in the future via the `ts` field on events
- I've responded to customer tickets asking why their runs are stuck
queued. Sometimes, the answer is that they scheduled their run in the
future
- For these scheduled runs, I'd like to make it clearer to the user why
their run is queued and not running
- I display a `scheduled at` when scheduled at exists and is offset from
it's queued (i.e in the future)
- I've added a (i) hover to provide some more detail. I'm not sold that
it's useful enough to justify its own existence. Open to edits or
removal!

After:
<img width="836" height="394" alt="Screenshot 2026-08-06 at 4 54 05 PM"
src="https://github.com/user-attachments/assets/98c5d4fc-b6d6-4f3a-af44-aa0865787fc4"
/>




Before:
<img width="749" height="411" alt="Screenshot 2026-08-05 at 3 20 12 PM"
src="https://github.com/user-attachments/assets/664cd60d-aa9b-4cc5-a407-0858dd8b0ab6"
/>

- I also validated this with crons, the other user of `ts` for
scheduling

## Release note

<!-- User-facing release note. Use "None" if this does not need release
notes. -->
- Surface scheduled at in the dashboard's run's page iff the event is
scheduled in the future

## Migration note

<!-- Upgrade, deployment, config, schema, or compatibility notes. Use
"None" if none. -->
None.

*[Check our Pull Request
Guidelines](https://github.com/inngest/inngest/blob/main/docs/PULL_REQUEST_GUIDELINES.md)*

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>