Docs: Add missing debugging page to App Router docs

docs/03-pages/01-building-your-application/06-configuring/13-debugging.mdx → docs/02-app/01-building-your-application/07-configuring/16-debugging.mdx

@@ -3,6 +3,8 @@ title: Debugging
 description: Learn how to debug your Next.js application with VS Code or Chrome DevTools.
 ---
 
+{/* The content of this doc is shared between the app and pages router. You can use the `<PagesOnly>Content</PagesOnly>` component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
+
 This documentation explains how you can debug your Next.js frontend and backend code with full source maps support using either the [VS Code debugger](https://code.visualstudio.com/docs/editor/debugging) or [Chrome DevTools](https://developers.google.com/web/tools/chrome-devtools).
 
 Any debugger that can attach to Node.js can also be used to debug a Next.js application. You can find more details in the Node.js [Debugging Guide](https://nodejs.org/en/docs/guides/debugging-getting-started/).

docs/03-pages/01-building-your-application/06-configuring/15-debugging.mdx

@@ -0,0 +1,7 @@
+---
+title: Debugging
+description: Learn how to debug your Next.js application with VS Code or Chrome DevTools.
+source: app/building-your-application/configuring/debugging
+---
+
+{/* DO NOT EDIT. The content of this doc is generated from the source above. To edit the content of this page, navigate to the source page in your editor. You can use the `<PagesOnly>Content</PagesOnly>` component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}