feat: replace deprecated logger methods

[juev]

Overview

Fixed: #524

What this PR does / why we need it

Just replace deprecated logger methods

Special notes for your reviewer

nope

[miklezzzz]

What for? As I see, we only return nil when there is an error in the Execute() call
And even if we get nil, shouldn't we return err then?

[juev]

A rather strange logic is used here,

1. We calculate the result hookResult, err := h.Execute(h.GetConfigVersion(), bc, "global", prefixedConfigValues, prefixedValues, logLabels)
2. Next, we check that the result is not null and there is a Usage to display the result.
3. Only after that we check for the error, and if there is one, return it.
4. And after that, we are already trying to fully access the hookResult fields, although theoretically it is possible that we get nil. As a result, instead of a mistake, we will get panic.
5. To avoid panic, we do a check on nil before accessing the hookResult fields. Since we've already checked for errors and they're no longer there, since we've got a hookResult with nil, we'll just exit the function with the result nil.

In a good way, after the calculation, you need to immediately check the error, if there is one, return it. Then check for nil, and then decide what to do, return a new error or return nil. And then process the result.

[miklezzzz]

yeah, the logic is strange, or even tightly coupled with what h.Execute() returns, but if there is no possibility of getting nil without errors, does it make sense to check? :)

[miklezzzz]

and if we check and get nil for the result, but w/o an error, it looks to me like an error condition 🤔 . I think we'd better return a custom error like 'something went wrong' instead of concealing the fact that we'd got nothing.

[juev]

It makes sense to think about it