fix: add write:repository scope to Gitea OAuth for webhook creation

[lamualfa]

Summary

• Add write:repository to Gitea OAuth scopes in all three configuration locations
• Add createGiteaWebhook utility to automatically create push webhooks in Gitea repos
• Auto-create webhooks when saving Gitea-linked applications or compose projects

Problem

The Gitea OAuth scopes across the codebase only requested read permissions. On GitHub, the repo scope grants full read/write access to repositories. On Gitea, repo maps to read:repository only. Creating webhooks via POST /api/v1/repos/{owner}/{repo}/hooks requires the write:repository scope.

Additionally, Dokploy never automatically creates webhooks in Gitea repositories (unlike the GitHub integration which uses GitHub Apps). Users had to manually configure webhooks in the Gitea UI pointing to Dokploy's deploy endpoint.

Changes

Scope fix (prerequisite)

File	Change
apps/dokploy/pages/api/providers/gitea/authorize.ts	Added write:repository to OAuth authorize scope
apps/dokploy/utils/gitea-utils.ts	Added write:repository to client-side OAuth scope
packages/server/src/db/schema/gitea.ts	Added write:repository to default scopes

Auto webhook creation (new feature)

File	Change
packages/server/src/utils/providers/gitea.ts	Added createGiteaWebhook() utility function
apps/dokploy/server/api/routers/application.ts	Call webhook creation in saveGiteaProvider handler
apps/dokploy/server/api/routers/compose.ts	Call webhook creation in update handler when sourceType is "gitea"

Implementation details

The createGiteaWebhook function:

• Refreshes the Gitea OAuth token before making API calls
• Checks for existing webhooks to avoid duplicates (matches by deploy path)
• Uses giteaInternalUrl when available for Docker co-hosted setups
• Constructs the Dokploy webhook URL from request headers (x-forwarded-proto + host)
• Uses the correct endpoint path based on resource type:
  • Applications: /api/deploy/{refreshToken}
  • Compose: /api/deploy/compose/{refreshToken}
• Errors are caught and logged to avoid blocking the save operation

Test plan

• Connect a Gitea provider with the updated scopes
• Create a compose linked to a Gitea repo, enable auto-deploy
• Verify a webhook is created in the Gitea repository (Settings > Webhooks)
• Verify webhook URL uses /api/deploy/compose/{token} path
• Push a commit and verify deployment triggers automatically
• Create an application linked to a Gitea repo
• Verify webhook URL uses /api/deploy/{token} path
• Save again and verify no duplicate webhooks are created
• Disconnect the Gitea provider and verify behavior
• Verify existing Gitea providers still work (existing tokens may need re-authentication to get the new write:repository scope)

Closes #4412