Revert "reduce_logs_for_kubelet_use_crio"

[uablrek]

This reverts commit b407dcd.

Fixes #3538

There may be a better way by detecting if cgroups are managed by systemd, but I have not enough knowledge of cadvisor, and not much time. So, the easy way out is to revert the commit causing the problem.

Further, I don't even know how to test it. I use K8s with cri-o, but cadvisor is vendored in K8s, so I don't know how to make K8s use this branch (I know howto build and test K8s from master though)

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[k8s-ci-robot]

Hi @uablrek. Thanks for your PR.

I'm waiting for a google member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[dims]

xref: #3457

[dims]

/ok-to-test

[dims]

/approve
/lgtm

[uablrek]

I have verified that the revert fixes the problem by copying cadvisor/container/crio/factory.go from this PR to K8s vendor/github.com/google/cadvisor/container/crio/factory.go.

Server Version: v1.31.0-alpha.3.185+2d4514e1690dc5-dirty
crio version 1.29.2

My metrics test works. They fail for crio without this PR (but works with containerd)