Step.7 monitor-updates: form-default fixes - critical_elapsed_days 7->3 + updateRing ''

Two form-default cleanups in the Step.7 YAML templates (GH Actions + ADO):

1. critical_elapsed_days default 7 -> 3
   The v0.7.99 release lowered the CRITICAL overall-elapsed tier from 7
   to 3 days. The inline script default was updated correctly
   ($criticalElapsedDays = 3) and the help-text reads "default 3 days",
   but the workflow_dispatch / pipeline-parameter default value was left
   at '7'. When an operator leaves the input untouched the form-default
   '7' is non-empty, so the override path runs and silently restores the
   old threshold.

2. updateRing default 'Wave1' -> '' (empty)
   Matches Step.8 + Step.9 which already use default: ''. The downstream
   guard `if ($scope -eq 'by-update-ring' -and $updateRing)` honours empty
   as "no filter", so behaviour is unchanged for the default scope='all'
   path. Removes the misleading "Wave1" value that suggested a real
   default exists when the operator switches to scope=by-update-ring.

Files changed:
  Automation-Pipeline-Examples/github-actions/Step.7_monitor-updates.yml
  Automation-Pipeline-Examples/azure-devops/Step.7_monitor-updates.yml

Author: NeilBird

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/Step.7_monitor-updates.yml

@@ -55,7 +55,7 @@ parameters:
     # accepts single ring, 'Prod;Ring2' list, or '***' wildcard (three stars - deliberate).
     displayName: "UpdateRing tag value (only used when scope=by-update-ring). Single, 'Prod;Ring2', or '***'."
     type: string
-    default: 'Wave1'
+    default: ''
 
   - name: longRunningStepHours
     displayName: 'PRIMARY signal (v0.7.96+). Flag in-flight runs whose CURRENT STEP has been running longer than this many hours.'
@@ -75,7 +75,7 @@ parameters:
   - name: criticalElapsedDays
     displayName: 'CRITICAL tier for overall-elapsed (v0.7.99+, default 3 days). Runs older than this get a :rotating_light: chip; older than 2x get a :skull: chip - strongest visual signal that human intervention is needed.'
     type: string
-    default: '7'
+    default: '3'
 
   - name: moduleVersion
     displayName: 'Pin AzLocal.UpdateManagement version (empty = latest from PSGallery). See Automation-Pipeline-Examples/README.md section 5 "Optional configuration".'

AzLocal.UpdateManagement/Automation-Pipeline-Examples/github-actions/Step.7_monitor-updates.yml

@@ -58,7 +58,7 @@ on:
         # or '***' (three stars - deliberate, not a typo) to match every cluster that HAS the UpdateRing tag set.
         description: "UpdateRing tag value (only used when scope=by-update-ring). Single ring, 'Prod;Ring2', or '***'."
         required: false
-        default: 'Wave1'
+        default: ''
       long_running_step_hours:
         description: 'PRIMARY signal (v0.7.96+). Flag in-flight runs whose CURRENT STEP has been running longer than this many hours (default 2). More accurate than overall-run elapsed for large clusters where a legitimate 12-node run can exceed 6-8h while each individual step ticks along normally.'
         required: false
@@ -74,7 +74,7 @@ on:
       critical_elapsed_days:
         description: 'CRITICAL tier for overall-elapsed (v0.7.99+, default 3 days). In-flight runs older than this get a :rotating_light: chip; older than 2x this get a :skull: chip. Strongest visual signal that human intervention is needed - a 19-day-stuck run will no longer be hidden behind a single "step errored" chip.'
         required: false
-        default: '7'
+        default: '3'
       module_version:
         description: 'Pin AzLocal.UpdateManagement version (empty = latest from PSGallery). See Automation-Pipeline-Examples/README.md section 5 "Optional configuration".'
         required: false