Extra logging displayed when verbose level is 0

[rashedkvm]

Description of problem

Extra logging data display while the log verbose level is not set or 0. See the example below.

Proposed solution

Option 1: Replace the internal LogSync implementation with github.com/go-logr/zapr

Option 2: Fix internal LogSync implementation so that verbose level is honored

Example

API Error name:tanzu apps error:workloads.carto.run "spring-petclinic" not found

Describe alternatives you've considered

N/A

Additional context

This issue was introduced while updating a newer version of the go-logr interface.