Add extra data in audit changes structure

What is the challenge?

Be able to handle value from audit without deduced the "impacted" json field changes and without process the current string provided in "value" by sending both value separately to let developer handle them on their side if they need to.

What is the impact?

Let developer handle those useful audit value out of the box. As it's only new field, the impact on current API usage must be low.

Describe your idea

To describe the idea, we provide a file in attachment.
The main idea would be to add 3 new fields in the "changes" structure. Those field could be made optional if you want to keep the current data format send to user.

In the audit request, you could for example add a new parameter named "extra_data" (or any other name) that would allow developer to get those information without impacting anything currently returned or they could be returned directly with current data but it would change the amount of data sent (and by extension extra fields by default)