Batch Reports Fail when a member report data not available.

Feature Request: Skip Batch Reports with Unavailable Data

Summary:
Enable batch reporting to skip member reports when required data is unavailable, allowing the remaining reports to run successfully. Notify users of any skipped reports and explain why they were excluded.

Problem Statement:
Currently, an entire batch can fail when a single member report requires data that is not available in the proposal. For example, a travel report may cause the batch to fail when the proposal contains no travel data. This prevents users from generating otherwise valid reports and requires manual adjustments to the batch.

Proposed Solution:
Check whether the required data is available for each member report during batch processing.
Skip member reports that cannot run because their required data is missing, and continue generating the remaining reports.
Provide a completion notification identifying skipped reports and explaining the missing data for each.
If no member reports can be generated, notify the user that no output was produced and explain why.
Limit this handling to unavailable-data scenarios; continue to surface other report-processing errors.

Benefits:
Prevents missing data in one member report from blocking the entire batch.
Reduces manual effort spent identifying and removing reports that cannot run.
Provides clear visibility into skipped reports and their missing data.
Improves the reliability and efficiency of batch reporting.