fix(webhooks): match scp-style repository URLs with any SSH user

[dannyqwertz]

Changes

Fixes an issue where webhooks failed for Gitea (or other Git providers) when using non-standard SSH users (like gitea@domain.com instead of git@domain.com), resulting in the dreaded "Nothing to do" message.

What was happening?

• Manual deployments worked fine because convertGitUrl() accepts any SSH user.
• However, the webhook path had a stricter check hardcoded specifically to git@....
• When Gitea sent a payload with gitea@..., Coolify couldn't match the repo to an existing app and skipped the deployment.

(Note: I originally thought this was related to custom ports, ssh:// prefixes, or .git suffixes, but after debugging it boiled down to just the hardcoded SSH user prefix.)

What changed?

• Updated the regex / string matching in the webhook payload handler to match the general user@host:path structure instead of enforcing git@. Now webhooks and manual deployments share the same matching expectations.

Issues

• Fixes [Bug]: Gitea webhook fails with "Nothing to do. No applications found..." on v4.1.2 #11120

Category

• Bug fix
• Improvement
• New feature
• Adding new one click service
• Fixing or updating existing one click service

AI Assistance

• AI was NOT used to create this PR
• AI was used (please describe below)

If AI was used:

• Tools used: Claude Code
• How extensively: Root cause analysis, the fix and the tests. Reviewed by me.

Testing

• Set up a Gitea repository with a custom SSH user (e.g. gitea@...).
• Trigger a push webhook.
• Coolify should now correctly find the corresponding app and start the build instead of dropping it with "Nothing to do".

Verified on a local instance with a real signed webhook: before the fix "Nothing to do...", after it the app is found and the deploy starts. A wrong repo or branch is still rejected.

Four tests added to WebhookHmacTest, including a negative one. All 33 pass.

Contributor Agreement

Important

• I have read and understood the contributor guidelines. If I have failed to follow any guideline, I understand that this PR may be closed without review.
• I have searched existing issues and pull requests (including closed ones) to ensure this isn't a duplicate.
• I have tested all the changes thoroughly with a local development instance of Coolify and I am confident that they will work as expected when a maintainer tests them.