Note that the returned hook events are changed to reflect the actual parameternames used to create or update the webhook. Specifically, the original`convertEvents` in the GitLab driver sets the value of `Hook.Events` with thefollowing mapping:```issues_events=true -> "issue"tag_push_events=true -> "tag"push_events=true -> "push"note_events=true -> "comment"merge_requests_events=true -> "merge"other options -> none```It seems the event name strings are arbitrary and not consistent acrossdifferent drivers, so the mapping itself doesn't provide much abstraction (ifany). More importantly, for all other drivers, `Hook.Events` contains nativeevents unrecognized by go-scm, but GitLab driver completely discards them. Thisis important to implement logics to "reconcile" webhooks (i.e., update only ifneeded) to sync the list of watched events. Therefore, this patch proposes`Hook.Events` returned by the hook-related functions in the GitLab driver tostore the option names if their values are true, e.g., `["issues_events","push_events", "confidential_issues_events"]`.This is a breaking change.