Pull-based Auto-deploy for Git providers

What problem will this feature address?

When using an isolated instance that has no accessible web hook, it's not possible to use the auto-deploy feature. This requires manual deployments for new versions of deployed applications, and is less than ideal for a development workflow.

Describe the solution you'd like

Ideally, I would like to be able to configure a schedule to fetch all my applications and check if the deployed commit is the latest version available in Git. If a newer commit is available, I would like a deployment task to be queued for completion similarly to how the push-based auto deploy workflow works.

The interval at which repositories are fetched should be configurable in settings.

Describe alternatives you've considered

Using the current push-based workflow was considered, but it requires opening access from GitHub.com (or other providers) to your Dokploy server, and in some environments this is not possible or not ideal (homelab, VPN, etc.).

Additional context

I am willing to do the PR, but I want feedback on the approach, configuration, and implications before making my PR.

Will you send a PR to implement it?

Maybe, need help

Start by reviewing the existing push-based auto-deploy workflow, deployment task queue, and application settings to identify the relevant entry points; the issue does not name specific files or tests. Define how scheduled Git checks, configurable intervals, and newer-commit detection should integrate with that workflow, then verify that isolated instances can queue deployments without inbound webhooks.