Add Request and Parent Action Context to Audit Log Entries

auditLog.list entries now include a request object with id and ipAddress fields, providing traceability back to the originating HTTP request. Fields are null for actions not triggered by an HTTP request (e.g. automations, system events).
auditLog.list entries now include a parentAction object with id, type, and name fields, linking audit entries to the larger operation that produced them (e.g. a bulk update). Fields are null when the entry is a standalone action.