Make e2e tests fail when controller logs contain unexpected errors

[wallrj]

Filter the logs for errors that are not expected.
e.g. Errors caused by the controller attempting to list navigator API resources before the navigator API has been registered.

Release note:

NONE

[wallrj]

In #96 (comment) @munnerz wrote:

As much as this does make it easier to read logs, I think it could also obscure information and make debugging tests harder, especially if the developer isn't aware that we filter logs out.

I still print the entire logs if the tests fail.
This new test is intended to alert us to unexpected errors in the log files, such as those that were caused by the missing event: patch verb in #95

[munnerz]

/lgtm
/approve

[jetstack-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: munnerz

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

• OWNERS [munnerz]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[jetstack-bot]

Automatic merge from submit-queue.