fix: Update pgbouncer mentions to supavisor and add warning to pgbouncer article (#20387)

* Update pgbouncer mentions to supavisor and add warning to pgbouncer article

* run prettier

* minor text update

apps/docs/pages/guides/getting-started/quickstarts/redwoodjs.mdx

@@ -94,8 +94,6 @@ export const meta = {
 
       <Admonition type="note">
 
-        Be sure to append `?pgbouncer=true` to the end of the `DATABASE_URL` connection string.
-
         Also, replace `[YOUR-PASSWORD]` and `[YOUR-PROJECT-REF]` with the password you used when creating your Supabase project and the project reference from the URL in your browser.
 
       </Admonition>

apps/www/_alternatives/supabase-vs-heroku-postgres.mdx

@@ -21,7 +21,7 @@ Supabase also offers managed Postgres, the main difference is that with each dep
 - Auth - [users can log in and out of your application](https://supabase.com/auth)
 - Functions - [deploy custom logic to the edge](https://supabase.com/edge-functions)
 - Storage - [serve large files and folders](https://supabase.com/storage)
-- PgBouncer - [connection pooling useful for serverless computing](https://supabase.com/docs/guides/database/connecting-to-postgres#connection-pool)
+- Supavisor - [connection pooling useful for serverless computing](https://supabase.com/docs/guides/database/connecting-to-postgres#connection-pooler)
 
 ## How are they similar?
 

apps/www/_blog/2021-04-02-supabase-pgbouncer.mdx

@@ -16,6 +16,11 @@ tags:
 date: '2021-04-02'
 ---
 
+<Admonition type="caution">
+  PgBouncer is now deprecated. Use
+  [Supavisor](https://supabase.com/blog/supavisor-postgres-connection-pooler) instead.
+</Admonition>
+
 Javascript Frameworks like [Next.js,](https://nextjs.org/) [Redwood](https://redwoodjs.com/), [Blitz](https://blitzjs.com/), and tools
 like [Prisma](https://www.prisma.io/docs/guides/deployment/deployment#pgbouncer) are all moving in one direction. Serverless.