ci: treat a too-early Context7 refresh as a skip

The first run of the refresh workflow failed. curl timed out after 60
seconds with no response, and later calls returned HTTP 400
{"error":"too-early","message":"... Minimum 10 days required between
updates."}. Context7 limits how often one library refreshes, so the
workflow failed on most pushes to main.

Allow 180 seconds for the response, print the body, and end with a
workflow notice when Context7 answers too-early. Any other non-200
answer still fails the job. Against the live API, the old script
exited 56 on the too-early answer and the new script exits 0 with the
notice.

Author: cardmagic

.github/workflows/context7-refresh.yml

@@ -23,8 +23,19 @@ jobs:
           CONTEXT7_API_KEY: ${{ secrets.CONTEXT7_API_KEY }}
           LIBRARY_NAME: /${{ github.repository }}
         run: |
-          curl --fail --silent --show-error --max-time 60 \
+          status=$(curl --silent --show-error --max-time 180 --output response.json --write-out '%{http_code}' \
             -X POST https://context7.com/api/v1/refresh \
             -H "Content-Type: application/json" \
             -H "Authorization: Bearer $CONTEXT7_API_KEY" \
-            -d "{\"libraryName\": \"$LIBRARY_NAME\"}"
+            -d "{\"libraryName\": \"$LIBRARY_NAME\"}")
+          cat response.json
+          echo
+          if [ "$status" = "200" ]; then
+            exit 0
+          fi
+          if [ "$status" = "400" ] && grep -q '"error":"too-early"' response.json; then
+            echo "::notice::Context7 refreshed $LIBRARY_NAME recently, so it skipped this refresh."
+            exit 0
+          fi
+          echo "::error::Context7 refresh failed with HTTP $status."
+          exit 1