Stagger the scheduled runs so the scraper repos never overlap

Every scraper repo ran its daily and Monday checks at 06:00 UTC. On Monday that
is the full README matrix in all four at once, up to about sixteen jobs against
one account, which is the burst that returned "Your system is sending too many
of this type of request" during the LinkedIn Python build. Valid inputs fail
with that error, so the runs would go red with nothing wrong in the code.

The Monday runs now start at 06:00, 06:20, 06:40 and 07:00 across
instagram-scraper-node, linkedin-scraper-node, linkedin-scraper-python and
amazon-scraper-node. This one runs at 06:20 UTC, daily and Monday alike.

The Monday run is recognised by comparing github.event.schedule to the cron
string, in the run name and in the plan job. Both comparisons are updated with
the cron line. Changing only the cron would have turned Monday into a plain
daily check with nothing failing to say so.

Author: anil-bd

.github/workflows/live.yml

@@ -6,9 +6,9 @@
 #     credit and about a minute, so a broken commit shows up at once.
 #     A newer push cancels a run still going for an older commit.
 #   by hand, from the Actions tab, to scrape whatever accounts you choose
-#   every day at 06:00 UTC except Monday: one profile, the async
+#   every day at 06:20 UTC except Monday: one profile, the async
 #     path, and the field table, about two credits
-#   every Monday at 06:00 UTC: the same, plus every code block in the README,
+#   every Monday at 06:20 UTC: the same, plus every code block in the README,
 #     about 35 credits and 30 minutes
 #
 # A slow day at the API shows up as a red run. Rerun it before reading more
@@ -20,14 +20,17 @@
 # the main repository commits; a copy of the repository just runs the checks.
 name: Live check
 
-run-name: "${{ github.event.schedule == '0 6 * * 1' && 'Weekly check: does every README block still work?' || github.event_name == 'schedule' && 'Daily check: is anything broken?' || github.event_name == 'push' && format('Push check: {0}', github.event.head_commit.message) || format('Scrape {0}', inputs.profiles) }}"
+run-name: "${{ github.event.schedule == '20 6 * * 1' && 'Weekly check: does every README block still work?' || github.event_name == 'schedule' && 'Daily check: is anything broken?' || github.event_name == 'push' && format('Push check: {0}', github.event.head_commit.message) || format('Scrape {0}', inputs.profiles) }}"
 
 on:
   push:
     branches: [main]
   schedule:
-    - cron: "0 6 * * 0,2-6"  # daily smoke, every day except Monday
-    - cron: "0 6 * * 1"    # Monday: the whole README
+    - cron: "20 6 * * 0,2-6"  # daily smoke, every day except Monday
+    - cron: "20 6 * * 1"    # Monday: the whole README. Staggered across the
+      # scraper repos (06:00, 06:20, 06:40, 07:00) so four full matrices never
+      # hit one account at once, which is what trips "too many requests".
+      # The two `== '20 6 * * 1'` checks below must match this line exactly.
   workflow_dispatch:
     inputs:
       profiles:
@@ -255,7 +258,7 @@ jobs:
   # instead of the sum of all of them.
   plan:
     name: List the README blocks
-    if: github.event.schedule == '0 6 * * 1' || inputs.validate == true
+    if: github.event.schedule == '20 6 * * 1' || inputs.validate == true
     runs-on: ubuntu-latest
     timeout-minutes: 5
     outputs: