chore(studio): improve Postgres upgrade experience

[dnywh]

What kind of change does this PR introduce?

Makes the Postgres upgrade experience clearer.

• Fixes DEPR-80
• Fixes DEPR-82

What is the current behavior?

• The ObjectsToBeDroppedWarning just links to the docs. It doesn’t make it clear that the user needs to remove the affected function(s).
• The Service Versions section doesn’t make it clear that this is where the user goes to upgrade Postgres
  • This is exacerbated by the fact that the API call to determine upgrade eligibility can take ~10 seconds

What is the new behavior?

Specifically for the ObjectsToBeDroppedWarning:

Before	After

To address upgrade clarity: the description for the Service Versions section has been amended.

Additional context

This is a follow up from #38904.

I would prefer that each line in ObjectsToBeDroppedWarning links out directly to its corresponding function. For example:

<Button size="tiny" type="default" asChild>
  <Link href={`/project/${ref}/database/functions?search=${obj}`}>Manage</Link>
</Button>

But the API only returns objects_to_be_dropped as an array of strings like:

• function public.test_noop_plv8 is using obsolete language plv8

That requires backend changes to provide the name of the function and name of the extension, not just the string.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
studio-self-hosted	Ready	Preview	Comment	Oct 5, 2025 11:49pm
studio-staging	Ready	Preview	Comment	Oct 5, 2025 11:49pm

6 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
cms	Ignored			Oct 5, 2025 11:49pm
studio	Ignored			Oct 5, 2025 11:49pm
design-system	Skipped			Oct 5, 2025 11:49pm
docs	Skipped			Oct 5, 2025 11:49pm
ui-library	Skipped			Oct 5, 2025 11:49pm
zone-www-dot-com	Skipped			Oct 5, 2025 11:49pm

[supabase]

This pull request has been ignored for the connected project xguihxuzqibwxjnimxev because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[coveralls]

coverage: 70.791%. remained the same
when pulling 51734c6 on dnywh/chore/improve-postgres-upgrade-experience
into 1ae6f4f on master.