docs: update code snippets in reference doocumentation

Author: SkyZeroZx

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

@@ -6,7 +6,7 @@ Two or more [components](guide/components) use the same element selector. Becaus
 
 This error occurs at runtime when you apply two selectors to a single node, each of which matches a different component, or when you apply a single selector to a node and it matches more than one component.
 
-```ts
+```angular-ts
 import {Component} from '@angular/core';
 
 @Component({

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

@@ -8,7 +8,7 @@ More information about hydration can be found in [this guide](guide/hydration).
 
 The following example will trigger the error.
 
-```typescript
+```angular-ts
 @Component({
   selector: 'app-example',
   template: '<div><span>world</span></div>',

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

@@ -6,7 +6,7 @@ More information about hydration can be found in [this guide](guide/hydration).
 
 The following examples will trigger the error.
 
-```typescript
+```angular-ts
 @Component({
   selector: 'dynamic',
   template: `

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

@@ -10,7 +10,7 @@ The following examples will trigger the error.
 
 In this example, the `ngSkipHydration` attribute is applied to a `<div>` using host bindings of a directive. Since the `<div>` doesn't act as a component host node, Angular will throw an error.
 
-```typescript
+```angular-ts
 @Directive({
   selector: '[dir]',
   host: {ngSkipHydration: 'true'},
@@ -34,7 +34,7 @@ class SimpleComponent {
 In this example, the `ngSkipHydration` is applied to a `<div>` as an attribute via a template.
 Since the `<div>` doesn't act as a component host node, Angular will throw an error.
 
-```typescript
+```angular-ts
 @Component({
   selector: 'app',
   template: `

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

@@ -2,7 +2,7 @@
 
 A track expression specified in the `@for` loop evaluated to duplicated keys for a given collection, ex.:
 
-```typescript
+```angular-ts
 @Component({
     template: `@for (item of items; track item.value) {{{item.value}}}`,
 })
@@ -21,7 +21,7 @@ There is also performance penalty associated with duplicated keys - internally A
 
 Change the tracking expression such that it uniquely identifies an item in a collection. In the discussed example the correct track expression would use the unique `key` property (`item.key`):
 
-```typescript
+```angular-ts
 @Component({
     template: `@for (item of items; track item.key) {{{item.value}}}`,
 })

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

@@ -2,7 +2,7 @@
 
 The identity track expression specified in the `@for` loop caused re-creation of the DOM corresponding to _all_ items. This is a very expensive operation that commonly occurs when working with immutable data structures. For example:
 
-```typescript
+```angular-ts
 @Component({
   template: `
     <button (click)="toggleAllDone()">All done!</button>
@@ -33,7 +33,7 @@ Apart from having a high performance penalty, re-creating the DOM tree results i
 
 Change the tracking expression such that it uniquely identifies an item in a collection, regardless of its object identity. In the discussed example, the correct track expression would use the unique `id` property (`item.id`):
 
-```typescript
+```angular-ts
 @Component({
   template: `
     <button (click)="toggleAllDone()">All done!</button>

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

@@ -3,42 +3,42 @@
 A component, directive, or pipe that is referenced by this component would require the compiler to add an import that would lead to a cycle of imports.
 For example, consider a scenario where a `ParentComponent` references a `ChildComponent` in its template:
 
-<docs-code header="parent.component.ts" language="angular-ts">
+```angular-ts {header:"parent.component.ts"}
 import {Component} from '@angular/core';
 import {ChildComponent} from './child.component';
 
 @Component({
-selector: 'app-parent',
-imports: [ChildComponent],
-template: '<app-child/>',
+  selector: 'app-parent',
+  imports: [ChildComponent],
+  template: '<app-child/>',
 })
 export class ParentComponent {}
-</docs-code>
+```
 
-<docs-code header="child.component.ts" language="angular-ts">
+```angular-ts {header:"child.component.ts"}
 import {Component, inject} from '@angular/core';
 import {ParentComponent} from './parent.component';
 
 @Component({
-selector: 'app-child',
-template: 'The child!',
+  selector: 'app-child',
+  template: 'The child!',
 })
 export class ChildComponent {
-private parent = inject(ParentComponent);
+  private parent = inject(ParentComponent);
 }
-</docs-code>
+```
 
 There is already an import from `child.component.ts` to `parent.component.ts` since the `ChildComponent` references the `ParentComponent` in its constructor.
 
 HELPFUL: The parent component's template contains `<child></child>`.
 The generated code for this template must therefore contain a reference to the `ChildComponent` class.
 In order to make this reference, the compiler would have to add an import from `parent.component.ts` to `child.component.ts`, which would cause an import cycle:
 
-<docs-code language="text">
+```text
 
 parent.component.ts -> child.component.ts -> parent.component.ts
 
-</docs-code>
+```
 
 ## Remote Scoping
 

adev/src/content/reference/extended-diagnostics/NG8101.md

@@ -2,7 +2,7 @@
 
 This diagnostic detects a backwards "banana-in-box" syntax for [two-way bindings](guide/templates/two-way-binding).
 
-```
+```html
 
 <user-viewer ([user])="loggedInUser" />
 ```
@@ -18,7 +18,7 @@ Fix the typo.
 As the name suggests, the banana `(` should go _inside_ the box `[]`.
 In this case:
 
-```
+```html
 
 <user-viewer [(user)]="loggedInUser" />
 ```

adev/src/content/reference/extended-diagnostics/NG8102.md

@@ -32,7 +32,7 @@ Double-check the type of the input and confirm whether it is actually expected t
 
 If the input should be nullable, add `null` or `undefined` to its type to indicate this.
 
-```ts
+```angular-ts
 
 import {Component} from '@angular/core';
 
@@ -49,7 +49,7 @@ username: string | null = 'Angelino';
 
 If the input should _not_ be nullable, delete the `??` operator and its right operand, since the value is guaranteed by TypeScript to always be non-nullable.
 
-```ts
+```angular-ts
 
 import {Component} from '@angular/core';
 

adev/src/content/reference/extended-diagnostics/NG8105.md

@@ -2,7 +2,7 @@
 
 This diagnostic is emitted when an expression used in `*ngFor` is missing the `let` keyword.
 
-```typescript
+```angular-ts
 import { Component } from '@angular/core';
 
 @Component({
@@ -22,7 +22,7 @@ A missing `let` is indicative of a syntax error in the `*ngFor` string. It also
 
 Add the missing `let` keyword.
 
-```typescript
+```angular-ts
 import { Component } from '@angular/core';
 
 @Component({