Add debug markers before and after mat-tab-group to isolate rendering issue

- Added cyan debug box before mat-tab-group element
- Added purple debug box after mat-tab-group closing tag
- If cyan shows but purple doesn't, mat-tab-group is consuming rendering but not displaying
- If both show, mat-tab-group is being skipped entirely
- This will help identify if mat-tab-group is the blocking element

Co-authored-by: renemadsen <[email protected]>

Author: Copilot

eform-client/src/app/plugins/modules/time-planning-pn/components/plannings/time-planning-actions/assigned-site/assigned-site-dialog.component.html

@@ -15,6 +15,9 @@ <h3 style="background: yellow; padding: 10px; margin: 10px 0;">
   <div style="background: orange; padding: 10px; margin: 10px 0; color: black;">
     DEBUG: About to render mat-tab-group
   </div>
+  <div style="background: cyan; padding: 10px; margin: 10px 0; color: black;">
+    DEBUG: CYAN - Testing if anything renders here between orange and mat-tab-group
+  </div>
   <mat-tab-group
     dynamicHeight="false"
   >
@@ -113,6 +116,9 @@ <h3 style="background: yellow; padding: 10px; margin: 10px 0;">
       </div>
     </mat-tab>
   </mat-tab-group>
+  <div style="background: purple; padding: 10px; margin: 10px 0; color: white;">
+    DEBUG: PURPLE - After mat-tab-group closing tag
+  </div>
 </div>
 <div mat-dialog-actions class="d-flex flex-row justify-content-end">
   <button