fixes extensions page to list all extensions #341

[JesseVent]

Feat: Add Interactive Packages Explorer Page

Description

This pull request adds a new Packages Explorer page (/packages) that connects directly to the registry's public RPC API (rpc/search_packages) to display a complete, searchable, sortable, and filterable table of all database packages.

Problem & Justification

Currently, the database.dev website only displays a handful of "Popular packages" on the homepage. There is no way for developers to browse, search, or inspect the full catalog of packages hosted in the registry.

• With only around 60 packages in total in the registry, it is currently impossible to see what extensions exist in the system without guessing handles or using custom search inputs.
• Developers need a dedicated explorer where they can discover extensions, check their versions, see what other extensions they require (e.g., pg_cron), and quickly copy the install command.

Key Features Implemented:

• Direct RPC Fetch: Queries the public database.dev API gateway to load all packages client-side.
• Advanced Filtering: Filter packages dynamically by search query (name, handle, description), publisher, and required extensions.
• Flexible Sorting: Sort columns (Name, Publisher, Creation Date) in ascending or descending order.
• Copy-to-Clipboard Action: Individual quick-copy action buttons that copy the CLI installation command with a visual success checkmark animation.
• Pagination: Navigate the package catalog with adjustable row limits (10/25/50).
• Navigation Integration: Added a "Packages" link to the main header navigation bar so the page is easily accessible.
• Responsive & Premium UI: Designed with clean badges, responsive table layout, hover states, and full dark/light mode compliance matching database.dev aesthetics.

[vercel]

@JesseVent is attempting to deploy a commit to the Supabase Team on Vercel.

A member of the Team first needs to authorize it.

[JesseVent]

Adding a few real-world examples of Trusted Language Extensions (TLEs) to the documentation to showcase how the registry is used:

• jvent@supa_privacy (for database anonymisation and masking)
• jvent@supa_profile (for table and column-level profiling)

These have been added under website/content/docs/install-a-package.mdx and website/content/docs/cli.mdx to illustrate dbdev add and dbdev install respectively.

Here's an illustration of the masking and profiling flow: