Summary: standardize on zap for logging in Tekton Results

Upstream issue: https://github.com/tektoncd/results/issues/272

Story (Required)

As a service provider trying to monitor Tekton Results I want all logs to use Zap so that all logged data has similar format and structure.

Background (Required)

Tekton results apiserver did not have a uniform means of logging to standard output. Using the zap logger everywhere uses this.

Out of scope

• Specifying the structure the logs to standard output.
• Changing how logs are configured by the apiserver.

Approach (Required)

• Identify all areas where the apiserver does not use zap to log data (ex - fmt.Printf)
• Replace any print statements with an equivalent log call at an appropriate level (typically debug or info).

Dependencies

• Initial config/setup of Zap in Results apiserver -

Acceptance Criteria  (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met