Add custom data and actor email

[hamedsh]

add actor_email

deleting a user from the Users table will make actor_id useless (its only a bunch of characters). by adding email as static content, it can be usable forever.

adding custom_data

most of the time, data change is not the only thing you need. for example in a real environment with a bunch of CLI actions and Crons, you need some additional records to specify the task that causes the change. by using custom_data, its possible to attach any data to the history log.
example:

with set_auditlog_custom_data(custom_data={"type": "management_command", "command": "clear_unused_records")}):
    target_function(obj)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (1ce39c0) 95.20% compared to head (6f0f9af) 95.33%.
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #603      +/-   ##
==========================================
+ Coverage   95.20%   95.33%   +0.13%     
==========================================
  Files          31       33       +2     
  Lines        1022     1051      +29     
==========================================
+ Hits          973     1002      +29     
  Misses         49       49              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[hramezani]

Thanks @hamedsh for this PR

The change for adding email filed is good.

The LogEntry model has an additional_data field and It can be used to provide additional data for the log record.
It has not been documented yet and we have an issue for documenting this field. probably you can create a PR for that.

@hamedsh please close this PR and create a PR for the actor email.
If you want to make more changes please create separate PR for them.