add video links (#7321)

Author: petercrocker

docs/docs/topics/branching.mdx

@@ -59,6 +59,10 @@ This flexibility allows different workflows—from quick data fixes to comprehen
 
 ### Branch-aware vs branch-agnostic
 
+<center>
+  <VideoPlayer url='https://youtu.be/VSVToQ2XtHs?si=MypRDj1P90qhWb7F' light />
+</center>
+
 Unlike Git where all content is branch-specific, Infrahub introduces a nuanced approach where some elements of the schema can bypass the branching system and be global to all branches. This design decision allows for more efficient management of system-level configurations while still maintaining isolation for user data.
 
 - **Branch-aware**: Records that are local to branches and follow the standard branching workflow. Changes to branch-aware records in one branch do not affect other branches until explicitly merged. Most user-created infrastructure data falls into this category.

docs/docs/topics/resource-manager.mdx

@@ -1,6 +1,7 @@
 ---
 title: Resource manager
 ---
+import VideoPlayer from '../../src/components/VideoPlayer';
 
 Resource managers in Infrahub automate the allocation of network resources from predefined pools, eliminating manual assignment and preventing conflicts across your infrastructure. This system ensures consistent resource allocation while maintaining complete visibility and control over your available resources.
 
@@ -24,6 +25,10 @@ This is due the dynamic nature of using resource managers and the idempotence of
 
 ### Branch-agnostic allocation
 
+<center>
+  <VideoPlayer url='https://youtu.be/F7tvLRQULdg?si=S83VyA0xmXHQGQqV' light />
+</center>
+
 One of the most powerful features of Infrahub's resource managers is branch-agnostic allocation. When you allocate a resource in any branch, that allocation is immediately reserved across all branches in your system. This prevents conflicts when merging branches and ensures resource uniqueness across your entire infrastructure.
 
 Consider this scenario: