Enhancement: Include Form Names in Signature Audit via API

urrently, the Signature Audit data available through the API includes file names associated with signed documents. While this provides basic traceability, it can be difficult for users to easily identify which form each file name corresponds to—especially when multiple forms share similar naming conventions or when file names are system-generated.

To improve usability and transparency, it would be beneficial for the API response to include the form names alongside or in place of the file names.

Proposed Enhancement:

Update the Signature Audit API response to include the form name for each document or file entry.

Maintain the existing file name field for backward compatibility, but add a new attribute such as formName or form_display_name.

Ensure the form name corresponds to the display name as configured in the form settings within the system.