fix: PR description cron schedule doesn't match implementation

[GitAddRemote]

User Story

As a developer reviewing the scheduled ETL jobs, I want the PR description to accurately reflect the deployed cron schedule so I'm not confused about when each step runs.

Definition of Done

• PR feat: ETL steps for terminals and terminal distances with hourly scheduler #220 description updated to show terminal-distances-sync is scheduled at minute 5 (5 * * * *), not minute 0

Acceptance Criteria

• PR description accurately documents both cron expressions: terminals at 0 * * * *, distances at 5 * * * *

Technical Elaboration

The PR description currently states both steps run at 0 * * * *. The actual implementation in catalog-etl.scheduler.ts offsets the distances step to 5 * * * * to ensure terminals populate first. The description needs to be corrected.

File: backend/src/modules/catalog-etl/schedulers/catalog-etl.scheduler.ts line 26

Design Elaboration

Doc-only fix — no code change needed.

[GitAddRemote]

PR #220 is already merged. The two-cron design described in that PR (terminals at 0 * * * *, distances at 5 * * * *) has been replaced wholesale by #221 / PR #289, which consolidates both into a single sequential scheduledTerminalEtl() at 0 * * * *. The schedule mismatch documented here no longer exists. Closing as resolved by #221.