fix(batch): add optional logger injection for BatchProcessors (#7553)

[Sujit-1509]

Issue number: closes #7553

Summary

Closes #7553.

Changes

This PR adds optional logger injection to the Batch Processing utility, allowing record-processing exceptions to be logged with their original traceback when desired.

Implementation

• Added an optional \logger: Logger | logging.Logger | None\ parameter to the batch processor hierarchy.

• Updated \ailure_handler()\ to emit a warning with \exc_info\ when:

  • a logger is provided, and
  • the exception contains a real traceback.

• Preserved existing behavior when no logger is supplied.

• Added regression tests covering:

  • exception logging with an injected logger,
  • backward compatibility when no logger is provided,
  • FIFO circuit-breaker scenarios to ensure synthetic exceptions are not logged.

Why logger injection?

This follows existing Powertools dependency-injection patterns and avoids introducing additional boolean configuration flags or undocumented APIs.

User Experience

Before:

• Record-processing exceptions were stored internally but not emitted through a customer logger.

After:

• Customers can provide a logger to the processor and receive warning logs with full traceback information for failed records.
• Existing behavior remains unchanged unless a logger is explicitly provided.

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud