🧹 chore: Avoid using any in catch clause in push-scheduler

[marcin2121]

🎯 What: The code health issue addressed was the use of : any type annotation in a catch block within app/api/cron/push-scheduler/route.ts.
💡 Why: Using : any suppresses TypeScript's type checking. By removing : any, the error defaults to unknown in modern TypeScript, enforcing safer type guards when interacting with the thrown value (such as safely checking error instanceof Error).
✅ Verification: Verified by confirming the file syntax is correct, running npm run lint and confirming no new errors or warnings were introduced in the modified file.
✨ Result: A safer, more robust codebase by eliminating un-typed exceptions in the catch block while maintaining functionality and gracefully extracting error messages for the response.

---

PR created automatically by Jules for task 10880298290203319261 started by @marcin2121

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.