Liveness and Readiness Checks for the Broker Ingress and Filter

[Harwayne]

Problem
The Broker Ingress and Filter Pods have no liveness or readiness checks. If for some reason, the HTTP server stops working, while the Pod is still running, the Broker will be broken until manual intervention by an operator to delete the Pod.

Persona:
Event Consumer

Exit Criteria
Liveness checks on both the Broker Ingress and Filter. Readiness check on the Broker Filter, that it only marks itself as ready if it can read the list of Triggers from the API server.

Additional context (optional)
Came about due to #1085.

[Harwayne]

/assign @grac3gao

[knative-prow-robot]

@Harwayne: GitHub didn't allow me to assign the following users: grac3gao.

Note that only knative members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @grac3gao

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[grac3gao-zz]

/assign @grac3gao

[akashrv]

/milestone v0.9.0