Verify JWT with legacy secret edge function toggle turns itself back on every time the function is updated.

# Bug report - [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 "Verify JWT with legacy secret" button, when I toggle it off manually after deploying a function, turns back on whenever i update the function. If this is desired behavior please reconsider as this resulted in me losing customers because my webhook was not working, and your frontend says "Recommendation: OFF with JWT and additional authorization logic implemented inside your function's code." which is what I do. ## To Reproduce Steps to reproduce the behavior, please provide code snippets or a repository: 1. Create and deploy a Supabase Edge Function 2. Turn "Verify JWT with legacy secret" OFF. 3. Download your function with the supabase cli with supabase functions download command. 4. Make code changes (might be optional: not tested) 5. Upload the new function with supabase functions deploy [your-updated-function] 6. The "Verify JWT with legacy secret" toggle is now ON. ## Expected behavior The "Verify JWT with legacy secret" toggle stays OFF when manually turned off, when the function is updated. ## Screenshots Here is the specific toggle I am talking about: <img width="1000" height="235" alt="Image" src="https://github.com/user-attachments/assets/63b28910-baf7-4f7a-ad97-a31331c0469a" /> ## System information Hosted by Supabase on supabase.com