Add webhook name field to improve webhook identification (#37025) (#37040)

Add an optional Name field to webhooks so users can give them
human-readable labels instead of relying only on URLs. The webhook
overview page now displays names when available, or falls back to the
URL for unnamed webhooks.

Fixes #37025

---------

Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>

modules/structs/hook.go

@@ -19,6 +19,8 @@ var ErrInvalidReceiveHook = errors.New("Invalid JSON payload received over webho
 type Hook struct {
 	// The unique identifier of the webhook
 	ID int64 `json:"id"`
+	// Optional human-readable name for the webhook
+	Name string `json:"name"`
 	// The type of the webhook (e.g., gitea, slack, discord)
 	Type string `json:"type"`
 	// Branch filter pattern to determine which branches trigger the webhook
@@ -66,6 +68,8 @@ type CreateHookOption struct {
 	// default: false
 	// Whether the webhook should be active upon creation
 	Active bool `json:"active"`
+	// Optional human-readable name for the webhook
+	Name string `json:"name" binding:"MaxSize(255)"`
 }
 
 // EditHookOption options when modify one hook
@@ -80,6 +84,8 @@ type EditHookOption struct {
 	AuthorizationHeader string `json:"authorization_header"`
 	// Whether the webhook is active and will be triggered
 	Active *bool `json:"active"`
+	// Optional human-readable name
+	Name *string `json:"name,omitzero" binding:"MaxSize(255)"`
 }
 
 // Payloader payload is some part of one hook