chore: Avoid naked return

[mrueg]

What this PR does / why we need it:
Make the code a bit more readable for folks not familiar with golang

How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)
None
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[k8s-ci-robot]

This issue is currently awaiting triage.

If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[rexagod]

/approve

Might be also worth wrapping naked errors for context (i.e., adding wrapcheck to

kube-state-metrics/.golangci.yml

Line 6 in d1e7179

enable:

)?

[rexagod]

/lgtm

We could to that in a separate PR, no need to block this.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mrueg, rexagod

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mrueg,rexagod]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mrueg]

/approve

Might be also worth wrapping naked errors for context (i.e., adding wrapcheck to

kube-state-metrics/.golangci.yml

Line 6 in d1e7179

enable:

)?
sounds like a useful addition.
feel free to add it! :)