Cannot inspect Egde logs in CI/CD

[riderx]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

When running supabase start in Github action The edge function starts, but we can't see its logs.
When running test against it and the test fails, we cannot see the reason of the fail in our code

To Reproduce

I made a reproduction repo for this:
https://github.com/riderx/supabase_edge_issue

You can see in the GitHub action it fails:
https://github.com/riderx/supabase_edge_issue/actions/runs/13354496001/job/37295330902
But we cannot see the logs of the edge functions.
We could run directly the Deno code outside the Edge worker, but this defeats the purpose of having the same env as production.

Expected behavior

Having a way to inspect the edge workers logs if the CI/CD failed.

[riderx]

Another example on why it's important: #1447
In my local test i was not up-to-date with images so i coudn't reproduce and understand the issue, now i replicate in local too but that was painful to understand