Session Inactivity timeout incorrectly set on deployment from branch

# 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 I have set auth.session.inactivity_timeout in my config.toml for my review branch to the following. ``` [remotes.review] project_id = "ratadfzsbjytbcemzthj" [remotes.review.auth] # The base URL of your website. Used as an allow-list for redirects and for constructing URLs used # in emails. site_url = "https://review--silnavigator.netlify.app/" [remotes.review.auth.sessions] inactivity_timeout = "10h0m0s" ``` When deployed via pushing to the branch the setting in the admin portal becomes 36000  In the deploy logs is the following ``` [sessions] timebox = "0s" -inactivity_timeout = "10s" +inactivity_timeout = "10h0m0s" ``` The value in the UI was 10 prior to deployment Either the UI is not correct in that the value is seconds OR the deployment is not correct. ## To Reproduce See above. ## Expected behavior A clear and concise description of what you expected to happen. ## Screenshots If applicable, add screenshots to help explain your problem. ## System information - OS: [e.g. macOS, Windows] - Browser (if applies) [e.g. chrome, safari] - Version of supabase-js: [e.g. 6.0.2] - Version of Node.js: [e.g. 10.10.0] ## Additional context Add any other context about the problem here.