Improve log messages and log configurations

[sayan-biswas]

1. Presently in tekton results, we do have zap logging configured in both API server and Watcher, but the configuration process in the knative based watcher is not uniform with configuration in the API server. Also the zap configuration in the API server doesn't take advantage of the atomic log level feature in zap and neither the ConfigMap is watched. As a result if we change the log level in the config it doesn't reflect in the API service immediately and it needs to be restarted to to use the updated log level.

2. Most of the log messages are not organised (warning, error, log) and also the message itself is too generic with few parameter to correctly identify the source of the issue. Specially in the logs API related methods.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.