Revert "fix(docs-infra): process mermaid code blocks (angular#54434)" (angular#54448)

This reverts commit 925c86a.
Reason for revert: broken CI after merging to main, see https://github.com/angular/angular/actions/runs/7908845750/job/21588824548.

PR Close angular#54448

Author: AndrewKushnir

adev/src/content/best-practices/runtime-performance/BUILD.bazel

@@ -5,6 +5,5 @@ generate_guides(
     srcs = glob([
         "*.md",
     ]),
-    mermaid_blocks = True,
     visibility = ["//adev:__subpackages__"],
 )

adev/src/content/best-practices/runtime-performance/skipping-subtrees.md

@@ -33,7 +33,8 @@ If Angular handles an event within a component without `OnPush` strategy, the fr
 
 As an example, if we set the change detection strategy of `MainComponent` to `OnPush` and the user interacts with a component outside the subtree with root `MainComponent`, Angular will check all the green components from the diagram below (`AppComponent`, `HeaderComponent`, `SearchComponent`, `ButtonComponent`) unless `MainComponent` receives new inputs:
 
-```mermaid
+<!-- TODO(josephperrott): enable this mermaid chart -->
+```
 graph TD;
     app[AppComponent] --- header[HeaderComponent];
     app --- main["MainComponent (OnPush)"];
@@ -61,7 +62,8 @@ As an example, if Angular handles an event within `MainComponent`, the framework
 
 <img alt="Change detection propagation from OnPush component" src="assets/content/images/best-practices/runtime-performance/on-push-trigger.svg">
 
-```mermaid
+<!-- TODO(josephperrott): enable this mermaid chart -->
+```
 graph TD;
     app[AppComponent] --- header[HeaderComponent];
     app --- main["MainComponent (OnPush)"];
@@ -87,7 +89,8 @@ If Angular handles an event in a component with OnPush, the framework will execu
 
 As an example, in the diagram below, Angular handles an event in `LoginComponent` which uses OnPush. Angular will invoke change detection in the entire component subtree including `MainComponent` (`LoginComponent`’s parent), even though `MainComponent` has `OnPush` as well. Angular checks `MainComponent` as well because `LoginComponent` is part of its view.
 
-```mermaid
+<!-- TODO(josephperrott): enable this mermaid chart -->
+```
 graph TD;
     app[AppComponent] --- header[HeaderComponent];
     app --- main["MainComponent (OnPush)"];
@@ -112,7 +115,8 @@ Angular will run change detection within a child component with `OnPush` when se
 
 For example, in the diagram below, `AppComponent` passes a new input to `MainComponent`, which has `OnPush`. Angular will run change detection in `MainComponent` but will not run change detection in `LoginComponent`, which also has `OnPush`, unless it receives new inputs as well.
 
-```mermaid
+<!-- TODO(josephperrott): enable this mermaid chart -->
+```
 graph TD;
     app[AppComponent] --- header[HeaderComponent];
     app --- main["MainComponent (OnPush)"];

adev/src/content/guide/components/BUILD.bazel

@@ -8,6 +8,5 @@ generate_guides(
     data = [
         "//adev/src/assets/images:components.svg",
     ],
-    mermaid_blocks = True,
     visibility = ["//adev:__subpackages__"],
 )

adev/src/content/guide/components/anatomy-of-components.md

@@ -87,7 +87,8 @@ component's **view**.
 
 In composing components in this way, **you can think of your Angular application as a tree of components**.
 
-```mermaid
+<!-- TODO(josephperrott): enable this mermaid chart -->
+```
 flowchart TD
     A[AccountSettings]-->B
     A-->C

adev/src/content/guide/components/lifecycle.md

@@ -302,7 +302,8 @@ The following diagrams show the execution order of Angular's lifecycle hooks.
 
 ### During initialization
 
-```mermaid
+<!-- TODO(josephperrott): enable this mermaid chart -->
+```
 graph TD;
 id[constructor]-->CHANGE;
 subgraph CHANGE [Change detection]
@@ -319,7 +320,8 @@ CHANGE--Rendering-->afterRender
 
 ### Subsequent updates
 
-```mermaid
+<!-- TODO(josephperrott): enable this mermaid chart -->
+```
 graph TD;
 subgraph CHANGE [Change detection]
 direction TB

adev/src/content/guide/di/BUILD.bazel

@@ -9,6 +9,5 @@ generate_guides(
         "//adev/src/assets/images:dependency_injection.svg",
         "//adev/src/content/examples/resolution-modifiers:src/app/self/self.component.ts",
     ],
-    mermaid_blocks = True,
     visibility = ["//adev:__subpackages__"],
 )

adev/src/content/guide/di/dependency-injection.md

@@ -119,7 +119,8 @@ When Angular discovers that a component depends on a service, it first checks if
 
 When all requested services have been resolved and returned, Angular can call the component's constructor with those services as arguments.
 
-```mermaid
+<!-- TODO(josephperrott): enable this mermaid chart -->
+```
 graph TD;
 subgraph Injector
 serviceA[Service A]

adev/src/content/guide/di/hierarchical-dependency-injection.md

@@ -92,7 +92,8 @@ For more information on `@Optional()`, see the [`@Optional()` section](#optional
 
 The following diagram represents the relationship between the `root` `ModuleInjector` and its parent injectors as the previous paragraphs describe.
 
-```mermaid
+<!-- TODO(josephperrott): enable this mermaid chart -->
+```
 stateDiagram-v2
     elementInjector: EnvironmentInjector\n(configured by Angular)\nhas special things like DomSanitizer => providedIn 'platform'
     rootInjector: root EnvironmentInjector\n(configured by AppConfig)\nhas things for your app => bootstrapApplication(..., AppConfig)
@@ -1111,6 +1112,7 @@ The root injector, marked as (A), uses _generic_ providers for details about `Ca
 
 3. Child component (C) as a child of Component (B). Component (C) defines its own, even _more specialized_ provider for `CarService`.
 
+<!-- TODO(josephperrott): enable this mermaid chart -->
 ```
 graph TD;
 subgraph COMPONENT_A[Component A]
@@ -1134,6 +1136,7 @@ When you resolve an instance of `Car` at the deepest component (C), its injector
 * An `Engine` resolved by injector (B)
 * Its `Tires` resolved by the root injector (A).
 
+<!-- TODO(josephperrott): enable this mermaid chart -->
 ```
 graph BT;
 

adev/src/content/guide/forms/BUILD.bazel

@@ -49,6 +49,5 @@ generate_guides(
         "//adev/src/content/examples/reactive-forms:src/app/profile-editor/profile-editor.component.html",
         "//adev/src/content/examples/reactive-forms:src/app/profile-editor/profile-editor.component.ts",
     ],
-    mermaid_blocks = True,
     visibility = ["//adev:__subpackages__"],
 )

adev/src/content/guide/forms/overview.md

@@ -107,7 +107,8 @@ The view-to-model diagram shows how data flows when an input field's value is ch
 1. The `FormControl` instance emits the new value through the `valueChanges` observable.
 1. Any subscribers to the `valueChanges` observable receive the new value.
 
-```mermaid
+<!-- TODO(josephperrott): enable this mermaid chart -->
+```
 flowchart TB
     U{User}
     I("&lt;input&gt;")
@@ -127,7 +128,8 @@ The model-to-view diagram shows how a programmatic change to the model is propag
 1. Any subscribers to the `valueChanges` observable receive the new value.
 1. The control value accessor on the form input element updates the element with the new value.
 
-```mermaid
+<!-- TODO(josephperrott): enable this mermaid chart -->
+```
 flowchart TB
     U{User}
     I(&lt;input&gt;)
@@ -154,7 +156,8 @@ The view-to-model diagram shows how data flows when an input field's value is ch
 1. The control value accessor also calls the `NgModel.viewToModelUpdate()` method which emits an `ngModelChange` event.
 1. Because the component template uses two-way data binding for the `favoriteColor` property, the `favoriteColor` property in the component is updated to the value emitted by the `ngModelChange` event \(*Blue*\).
 
-```mermaid
+<!-- TODO(josephperrott): enable this mermaid chart -->
+```
 flowchart TB
     U{User}
     I(&lt;input&gt;)
@@ -185,7 +188,8 @@ The model-to-view diagram shows how data flows from model to view when the `favo
 1. Any subscribers to the `valueChanges` observable receive the new value.
 1. The control value accessor updates the form input element in the view with the latest `favoriteColor` value.
 
-```mermaid
+<!-- TODO(josephperrott): enable this mermaid chart -->
+```
 flowchart TB
     C(Component)
     P(Property bound to NgModel)