[cleaner] Raise error for long filenames

[dtzhou2]

Partially resolves issue #3018
This fix just adds a debug error message stating that the filename was too long to obfuscate.
Does not terminate the cleaner or change the filename, thinking of more complete fix now.

Signed-off-by: Daniel Zhou [email protected]

---

Please place an 'X' inside each '[]' to confirm you adhere to our Contributor Guidelines

• [ X] Is the commit message split over multiple lines and hard-wrapped at 72 characters?
• [ X] Is the subject and message clear and concise?
• [ X] Does the subject start with [plugin_name] if submitting a plugin patch or a [section_name] if part of the core sosreport code?
• [ X] Does the commit contain a Signed-off-by: First Lastname [email protected]?
• [ X] Are any related Issues or existing PRs properly referenced via a Closes (Issue) or Resolved (PR) line?

[packit-as-a-service]

Congratulations! One of the builds has completed. 🍾

You can install the built RPMs by following these steps:

• sudo yum install -y dnf-plugins-core on RHEL 8
• sudo dnf install -y dnf-plugins-core on Fedora
• dnf copr enable packit/sosreport-sos-3299
• And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.

[TurboTurtle]

Logging this is fine and helpful, but there are 2 separate concerns here I have.

1. This doesn't actually log when a failure occurs. It preemptively does so, and still continues on with the failing code.
2. Related to that, this should ideally capture the failing code (e.g. in a try block) to gracefully fail out of the obfuscation attempt and then log the message.

[arif-ali]

@dtzhou2 you still working on this PR at all?