Add Github Webhook Secret support

What problem will this feature address?

Currently, any deploy URL can be triggered by any client, as soon as they get access to the webhook url.

Since the refreshToken is stored in the URL, it makes it possible to intercept this url, then a bad actor could re-use this token to spam deployments, causing potential server overload.

Describe the solution you'd like

Adding support for handling GitHub's Webhooks Secret :

Would make this public url for deployment more secure, as the secret will need to match what Dokploy would provide.

The steps to implement such validation is described here : https://docs.github.com/en/webhooks/using-webhooks/validating-webhook-deliveries

I guess such logic would live next to this : https://github.com/Dokploy/dokploy/blob/569d43ae7fcd307a477983f17fcfbb33a656d204/apps/dokploy/pages/api/deploy/%5BrefreshToken%5D.ts#L25

Describe alternatives you've considered

Currently, I guess the only alternative to provide such level of validation would be to have a custom url doing this same logic, which would then call the dokploy cli to deploy the application.

Obviously, this seems way over the top, and I would rather risk having a public webhook url rather than creating such workaround.

Additional context

While unrelated (I should maybe create another issue for that), it doesn't help that GitHub Webhook support is basically unusable for the workflow of the Registry package events (screenshot below), as it create superfluous events with payloads that Dokploy does not support

Will you send a PR to implement it?

Maybe, need help

Start with apps/dokploy/pages/api/deploy/[refreshToken].ts at the linked line, then read GitHub's webhook delivery validation guidance. Determine how the endpoint can validate the configured webhook secret before deployment requests are accepted. Done means requests with a matching secret are supported while invalid or absent signatures are rejected.