Enhance audit log to support log different event such as login, configuration, user change etc

[stonezdj]

Many users concern about the audit log to log important security events in the Harbor, so that every security incident can be traceable. They want to enrich the event type to add the following:

1. User login
2. User create/delete
3. Project member add/remove, including user and group member
4. Configuration change, including system-level config and project-level configure
5. Project policy change: include the tag retention, and immutable policy change
6. Audit log cleanup schedule or execution

Issue list

#20367
#20295
#20293
#20292
#18351
#15134
#14277
#4426
#11996

Subtasks

• Add new extentensible framework for audit log to support multiple event type. #21205
• Add UI to query and dispaly audit log with new format #21202
• Create configuration to enable/disable a specific operation+resource  #21201
• x-forwarded-for support for logging true user IP #20367
• Add Successful Standalone Login to Harbor GUI to Audit Log (TSA Security Act UK) #20295
• Make username of person/account logging in (unsuccessful attempt) (currently in core.log) in audit.log (TSA Security Act UK) #20293
• Adding or deleting user events are not registered #18351
• Add audit_log to log project member change #21204
• Add audit_log to log the configuration change  #21203

[reasonerjt]

I don't think we wanna resolve all the issues in the description area.
The key to implement in v2.13.0 is a extensible framework and data structure to enable logging different events. In terms of what event types will be included, we will decide it after reviewing the design.