refactor(rest): improve logging in FossologyRestClient

[Mohamed-hanfy]

Issue:

This PR enhances logging and error handling in the FossologyRestClient to improve debugging and maintainability. It addresses inconsistent error messages and insufficient debug information when failures occur.

Changes:

• Improved Debug Logging:

  • Added detailed debug logs before making HTTP requests (e.g., upload, scan, report generation).
  • Included relevant context such as filename, uploadId, jobId, reportId, and shaValue.

• Enhanced Error Handling:

  • Improved exception messages for RestClientException, NumberFormatException, and unexpected cases.
  • Logs now provide clear descriptions of failures, including HTTP status codes and response bodies when available.
  • Added debug logs for detailed error stack traces.

• Fixed Typos and Formatting Issues:

  • Corrected spelling mistakes in log messages (thann → than).
  • Standardized log message formats for consistency.

How to Test:

1. Run the Fossology integration and attempt file uploads, scans, and reports.
2. Trigger error scenarios (e.g., incorrect upload IDs, invalid responses, failed HTTP requests).
3. Check logs to ensure clear and informative messages are displayed.

Suggested Reviewers:

@GMishx @EttingerK @rudra-superrr

Checklist:

• All related issues are referenced in commit messages and in PR.
• Logging improvements do not introduce performance overhead.
• No new dependencies were added.

[GMishx]

Changes looks good.

[GMishx]

@Mohamed-hanfy , please change the commit message to follow conventional commits. You can read our docs: https://eclipse.dev/sw360/docs/development/dev-semantic-commits/

[Mohamed-hanfy]

hello @GMishx,
I've updated the commit message to follow the semantic commit guidelines as requested. Thanks for the review!