fix: increase the receive_timeout to 24 hours for delete job

[fuziontech]

Problem

We timeout waiting for lightweight deletes to finish on CH deleting events

Changes

This will basically just let the job wait for the delete event to finish (should always finish in 24 hours) - if the workflow is killed it will pick up from the waiting on mutation node anyways so just lean into that

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Does this work well for both Cloud and self-hosted?

How did you test this code?

[greptile-apps]

PR Summary

This PR increases the ClickHouse delete job timeout from 10 minutes to 24 hours to prevent timeouts during event deletion operations.

• Increased receive_timeout to 24 hours in dags/deletes.py to allow delete jobs to complete without timing out
• Removed lightweight_deletes_sync config option since it's now handled at cluster level
• Set mutations_sync and lightweight_deletes_sync to 0 for async operation mode
• Updated documentation for max_execution_time parameter to be more general

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}