feat: add payout report handling in APIUtils and update related components

[VenuMadhav2541]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

Added Payout Report functionality to enable comprehensive reporting capabilities for payout transactions. This implementation follows the same architectural patterns established in the existing payments and refunds reporting features, ensuring consistency across the platform.

Key Changes:

• Integrated GenerateReport component with PAYOUT_REPORT entity in the Payouts list page
• Added conditional rendering based on generateReport and email feature flags
• Implemented report generation button in the payouts header section
• Ensured proper data validation and API integration for payout report requests
• Maintained UI/UX consistency with existing payment and refund report features

Motivation and Context

Problem Statement:

• Users lacked comprehensive reporting capabilities for payout transactions
• Manual data extraction and analysis was time-consuming and error-prone
• Missing feature parity across transaction types (payments and refunds had reports, payouts didn't)
• Difficult to perform financial reconciliation and audit trails for payout operations

Business Value:

• Enables data-driven decision making for payout operations
• Supports compliance and regulatory reporting requirements
• Improves operational efficiency through automated report generation
• Provides consistent user experience across all transaction types in the platform

How did you test it?

Manual Testing:

• Verified report generation button appears when feature flags are enabled (generateReport and email)

• Report generation request details

Integration Testing:

• Tested end-to-end report generation workflow with backend API
• Verified proper data formatting and export functionality
• Confirmed feature flag behavior in different environments

Where to test it?

• INTEG
• SANDBOX
• PROD

Checklist

• I ran npm run re:build
• I reviewed submitted code
• I added unit tests for my changes where possible

[semanticdiff-com]

Review changes with