docs: replace @debugging tag with proper Markdown syntax

Author: SkyZeroZx

adev/src/content/reference/errors/NG0602.md

@@ -54,7 +54,7 @@ Alternatively, if this is not possible, consider manually subscribing to the obs
 As a last resort, use `untracked` to leave the reactive context.
 Be careful as leaving the reactive context can result in signal reads to be ignored inside `untracked`.
 
-@debugging
+### Debugging the error
 
 The error message mentions the function that was unexpectedly called.
 Look for this function call in your application code.

adev/src/content/reference/errors/NG0913.md

@@ -8,7 +8,8 @@ When images are loaded, the **intrinsic size** of the downloaded file is checked
 
 The largest contentful element on a page during load is considered the "LCP Element", which relates to [Largest Contentful Paint](https://web.dev/lcp/), one of the Core Web Vitals. Lazy loading an LCP element will have a strong negative effect on page performance. With this strategy, the browser has to complete layout calculations to determine whether the element is in the viewport before starting the image download. As a result, a warning is triggered when Angular detects that the LCP element has been given the `loading="lazy"` attribute.
 
-@debugging
+### Debugging the error
+
 Use the image URL provided in the console warning to find the `<img>` element in question.
 
 ### Ways to fix oversized images