Dropdown clipped by viewport in Edge Function Logs & foreign key modal (no scroll to reach content)

# Bug report <!-- ⚠️ We receive a lot of bug reports which have already been solved or discussed. If you are looking for help, please try these first: - Docs: https://docs.supabase.com - Discussions: https://github.com/supabase/supabase/discussions - Discord: https://discord.supabase.com Before opening a bug report, please verify the following: --> - [x] I confirm this is a bug with Supabase, not with my own application. - [x] I confirm I have searched the [Docs](https://docs.supabase.com), GitHub [Discussions](https://github.com/supabase/supabase/discussions), and [Discord](https://discord.supabase.com). ## Describe the bug The Severity filter dropdown in Edge Function Logs gets clipped by the viewport at certain window heights, with no internal scroll, making the Apply button unreachable without resizing the browser window. ## To Reproduce Steps to reproduce the behavior, please provide code snippets or a repository: 1. Go to Edge Functions → [any function] → Logs 2. Click the "Severity" filter button 3. At normal/smaller window height, the dropdown extends below the visible viewport 4. Dropdown has no internal scrollbar, so Apply button is inaccessible ## Expected behavior Dropdown should either reposition itself above the trigger when there's insufficient space below, or have an internal scroll so all options + Apply button remain reachable ## Screenshots If applicable, add screenshots to help explain your problem. <img width="1401" height="706" alt="Image" src="https://github.com/user-attachments/assets/eddf64a0-ea2f-4215-8a8c-6ebb3bc08393" /> ## System information - OS: Windows - Browser: Chrome - Version of supabase-js: N/A — this bug is in the Supabase Dashboard (web app), not the client library - Version of Node.js: N/A — issue reproduced directly in-browser, no local project involved - Dashboard URL: https://supabase.com/dashboard/project/vkwefjpfuzlpopdocdgm/functions/process-reminder-notifications/logs ## Additional context I found this issue in mult…