Problem

This updates Services::Web to listen to all system events by default to bring the expected behavior in line with the documentation. From the repo hooks docs (emphasis mine):

For a Hook to go through, the Hook needs to be configured to trigger for an event, and the Service has to listen to it. Most of the Services only listen for push events. However, the generic Web Service listens for all events.

In testing with RequestBin we found the actual behavior of the web service to only listen for push events. This observation is backed up with the JSON hook representation (seen below), where the only event listed is push:

{
    name: "web",
    events: [
        "push"
    ],
    supported_events: [
        "commit_comment",
        "create",
        "delete",
        "download",
        "follow",
        "fork",
        "fork_apply",
        "gist",
        "gollum",
        "issue_comment",
        "issues",
        "member",
        "public",
        "pull_request",
        "pull_request_review_comment",
        "push",
        "status",
        "team_add",
        "watch"
    ],
    schema: [
        [
            "string",
            "url"
        ],
        [
            "string",
            "secret"
        ],
        [
            "string",
            "content_type"
        ],
        [
            "string",
            "ssl_version"
        ],
        [
            "boolean",
            "insecure_ssl"
        ]
    ]
}

Fix

Added Service::ALL_EVENTS as the default_events so the web services would listen for all supported events.

Tests

Expanded test coverage for the types of events that are listened to and a single test for an event other than push.

• Added a test to ensure the services listens to all events by comparing Service::ALL_EVENTS to the default_events
• Added an issue test to make sure the payload comes through as expected.