docs(angular): 📝 add "fake it till you mock it" chapter

.github/workflows/test.yml

@@ -20,7 +20,7 @@ env:
 jobs:
   test-and-deploy:
     name: 🚀 Test & Deploy
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     steps:
       - uses: actions/checkout@v4
         with:

.github/workflows/update-snapshots.yml

@@ -8,7 +8,7 @@ env:
 jobs:
   update-snapshots:
     name: 🌅 Update Snapshots
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     steps:
       - uses: actions/checkout@v4
         with:

apps/cookbook/docs/angular/01-testing/01-beyond-unit-vs-integration/index.mdx

@@ -159,7 +159,7 @@ Given Wide test properties, one might think that they should simply be avoided.
 - They are more [symmetric to production](../../02-glossary.md#symmetric-to-production), and [predictive](../../02-glossary.md#predictive), thus more reassuring.
 - They are more [structure-insensitive](../../02-glossary.md#structure-insensitive) _(e.g. you can refactor your code without breaking them)_.
 
-## ⚖️ Comparing Narrow and Wide Tests
+## ⚖️ Comparing Narrow and Wide Tests {#comparing-narrow-and-wide-tests}
 
 | Property                                                                | Narrow Tests          | Wide Tests            |
 | ----------------------------------------------------------------------- | --------------------- | --------------------- |