docs(misc): add videos to feature pages

Author: juristr

docs/nx-cloud/features/explain-with-ai.md

@@ -1,5 +1,10 @@
 # Explain with AI (beta)
 
+{% youtube
+src="https://youtu.be/g2m9cHp-O-Q"
+title="Explain with AI"
+ /%}
+
 "Explain with AI" helps you understand complex errors more quickly by providing AI-powered error resolution steps. This is made possible by using additional context from Nx targets and metadata, allowing for more accurate and relevant responses.
 
 ![explain with ai](/nx-cloud/features/explain-with-ai.avif)

docs/shared/features/automate-updating-dependencies.md

@@ -1,16 +1,16 @@
 # Automate Updating Dependencies
 
+{% youtube
+src="https://youtu.be/A0FjwsTlZ8A"
+title="How Automated Code Migrations Work"
+/%}
+
 Keeping your tooling up to date is crucial for the health of your project. Tooling maintenance work can be tedious and time consuming, though. The **Nx migrate** functionality provides a way for you to
 
 - automatically update your **`package.json` dependencies**
 - migrate your **configuration files** (e.g. Jest, ESLint, Nx config)
 - **adjust your source code** to match the new versions of packages (e.g., migrating across breaking changes)
 
-{% youtube
-src="https://www.youtube.com/embed/Ss6MfcXi0jE"
-title="How Automated Code Migrations Work"
-/%}
-
 To update your workspace, run:
 
 ```shell

docs/shared/features/cache-task-results.md

@@ -1,5 +1,7 @@
 # Cache Task Results
 
+{% youtube src="https://youtu.be/o-6jb78uuP0" title="Remote Caching with Nx Replay" /%}
+
 Rebuilding and retesting the same code repeatedly is costly. Nx offers a sophisticated and battle-tested computation caching system that ensures **code is never rebuilt twice**. This:
 
 - drastically **speeds up your task execution times** while developing locally and even more [in CI](/ci/features/remote-cache)

docs/shared/features/generate-code.md

@@ -1,5 +1,7 @@
 # Generate Code
 
+{% youtube src="https://youtu.be/hSM6MgWOYr8" title="Generate Code" /%}
+
 Code generators are like automation scripts designed to streamline your workflow. Essentially, they are TypeScript functions that accept parameters and help boost your productivity by:
 
 - Allowing you to **scaffold new projects** or **augment existing projects** with new features, like [adding Storybook support](/nx-api/storybook#generating-storybook-configuration)

docs/shared/features/remote-cache.md

@@ -1,5 +1,10 @@
 # Use Remote Caching (Nx Replay)
 
+{% youtube
+src="https://youtu.be/NF1__N_snog"
+title="Remote Caching with Nx Replay"
+ /%}
+
 Repeatedly rebuilding and retesting the same code is costly — not just in terms of wasted resources, but also in terms of developer time. To solve this, Nx includes a sophisticated computation caching system that ensures **code is never rebuilt twice**, saving you both time and resources.
 
 ![Diagram showing Teika sharing his cache with CI, Kimiko and James](/shared/images/dte/distributed-caching.svg)

docs/shared/features/run-tasks.md

@@ -1,5 +1,7 @@
 # Run Tasks
 
+{% youtube src="https://youtu.be/aEdfYiA5U34" title="Run tasks with Nx" /%}
+
 In a monorepo setup, you don't just run tasks for a single project; you might have hundreds to manage. To help with this, Nx provides a powerful task runner that allows you to:
 
 - easily **run multiple targets** for multiple projects **in parallel**

docs/shared/using-nx/affected.md

@@ -1,5 +1,10 @@
 # Run Only Tasks Affected by a PR
 
+{% youtube
+src="https://youtu.be/q-cu5Lw3DoE"
+title="Only Run Tasks for Projects That Changed"
+ /%}
+
 As your workspace grows, re-testing, re-building, and re-linting **all projects becomes too slow**. To address this, Nx comes with an "affected" command. Using this command, Nx
 
 - determines the minimum set of **projects that are affected by the change**