fix(ci): tidy azure-pipelines-cd review nits

- Replace the DST-fragile `1am PST = 09:00 UTC` cron comment with a
  UTC-anchored phrasing that also acknowledges the \~1am PT / \~2am
  PDT seasonal drift, so readers do not assume the schedule tracks
  Pacific time year-round.
- Drop the unused `undeployedTags` stage variable from the Package
  stage. It was bound to the Check stage output but never consumed
  downstream — the Package stage's own `download-github-releases.mjs`
  invocation re-enumerates undeployed releases from the local git tag
  set, so removing the captured variable also removes the implicit
  expectation that the two stages share that list. The script still
  emits the output via `##vso[task.setvariable]` for visibility in
  the Check stage log.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: janechu

azure-pipelines-cd.yml

@@ -2,7 +2,7 @@ trigger: none
 pr: none
 
 schedules:
-- cron: '0 9 * * *' # 1am PST = 09:00 UTC.
+- cron: '0 9 * * *' # 09:00 UTC daily (~1am Pacific in standard time, ~2am during DST).
   displayName: Daily npm/crates publish from GitHub Releases
   branches:
     include:
@@ -79,7 +79,6 @@ extends:
       condition: eq(dependencies.Check.outputs['CheckVersion.deploymentCheck.needsDeployment'], 'true')
       variables:
         npm_config_cache: $(Pipeline.Workspace)/.npm
-        undeployedTags: $[ stageDependencies.Check.CheckVersion.outputs['deploymentCheck.undeployedTags'] ]
       jobs:
       - job: Deploy
         steps: