Only print walk error when not nil

[glynternet]

During the hefty rebase of #47 I accidentally left a couple of log lines in the wrong place meaning we would log an error log line whenever a nested archive would be walked.

This PR fixes up those logs by:

• Removing error log on every nested archive walk, replacing it with the wrapping of a bubbled up error in the top level Identify method.
• Removing the "Found finding in what appeared to be an obfuscated jar..." log line, which lives at

  log4j-sniffer/pkg/crawl/identify.go

  Line 188 in 28f06a3

  i.printInfoFinding("Found finding in what appeared to be an obfuscated jar at %s", path)

  with the handling of obfuscated results. I've added an issue for handling obfuscation at nested levels.

[changelog-app]

Generate changelog in changelog/@unreleased

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

A small logging bug has been fixed where for nested archives, an error log line would be emitted for all results, regardless of whether there was an error or not.

Check the box to generate changelog(s)

• Generate changelog entry

[hpryce]

👍