Unwrap errors

[olegsu]

Related to #388

This PR includes also:

1. Update all the logger calls where the regular go vet would report
2. Update the CI script golangci-lint configuration to run custom print.funcs

Why update vet with print.funcs?

Normally go vet runs on a lot of functions signatures (the full list go tool vet help printf), but not the one that in logp
To overcome this go vet allow to add additional functions to check.
By setting -printfuncs="Infof,Debugf,Warnf,Errorf,Fatalf,Panicf,DPanicf" we can make sure that all the logger calls are covered

Run locally

• Install golangci-lint
• Run golangci-lint run

Output

When having formatting issues, for example l.log.Infof("Waiting for initial reconfiguration from Fleet server... %s")
You would see

Additional Reading

• go vet cmd
• wrap-unwrap-errors
• golang ci - go vet

[mergify]

This pull request does not have a backport label. Could you fix it @olegsu? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit
  NOTE: backport-skip has been added to this pull request.

[oren-zohar]

Love the use of go vet printfuncs

[oren-zohar]

💯

[oren-zohar]

should probably be part of unit-test.yml so we'll run it only once

[olegsu]

I see we are using golangci-lint. Will update its config

[github-actions]

Cloudbeat CI 🤖

Allure Report: http://csp-allure-reports.s3.amazonaws.com/allure_reports/cloudbeat/prs/404/index.html

[oren-zohar]

should probably be part of unit-test.yml so we'll run it only once

[oren-zohar]

looks great, can you please share a screenshot of what the logs looks like for one of the edited logs?

[oren-zohar]

Why not include them if we are passing all of the analyzers? (Tested locally and appears to pass)

[olegsu]

Missed this one