[DEV-15460] mitigate python stack trace returned to download user

[james-at-kc]

Description:

If an exception is encountered during the download generation process the /api/v2/download/status endpoint will return the Python stack trace in the API response’s message field. This can expose information about the API deployment environment.

Technical Details:

Log these error message for future reference, but remove from the API response.

Requirements for PR Merge:

1. Unit & integration tests updated
2. N/A - API documentation updated (examples listed below)
   1. API Contracts
   2. API UI
   3. Comments
3. N/A - Data validation completed (examples listed below)
   1. Does this work well with the current frontend? Or is the frontend aware of a needed change?
   2. Is performance impacted in the changes (e.g., API, pipeline, downloads, etc.)?
   3. Is the expected data returned with the expected format?
4. N/A - Appropriate Operations ticket(s) created
5. Jira Ticket(s)
   1. DEV-15460

Explain N/A in above checklist:

N/A for number 2 - no change to API - generic message returned instead of stack trace
N/A for number 3 - no change to frontend, performance nor expected data
N/A for number 4 - No operations tickets required - straight merge to qat then default promotion to prod.

[zachflanders-frb]

Looks good, I left one non blocking comment for consideration.