Run export history as a background process/task

The export worker offloads export operations to the background.

• Initiate history export functionality in the background when a user requests an export.

• Triggers sending email to project admin and user who made the request when export is completed or if an error occurred

• Allow history export based on filters to the export functionality based on workflow, status, received date, last activity, and search string.

• Completed exports are stored in a bucket defined in the storage service.

• The data should be exported in a .json structure considering different work orders have varying number of steps.

• Naming convention: Lightning_history_export_{{uuid_of_export}}.json??

• Specified download path should be a signed URL i.e. download(path) => signed url

• Relevant status of exports are :completed, :in_progress, :failed, :expired.

• Set expiry_date of the file to a 24 hour period after the history was exported.

No files, tests, or entry points are named. Start by locating the export worker and storage service, then trace how history filters and export requests are handled. Done requires background execution, completion or failure emails, filtered JSON files in the configured bucket, signed download URLs, the listed statuses, and 24-hour expiry.