Create access logs from requests

[rgraber]

Checklist

1. If you've added code that should be tested, add tests
2. If you've changed APIs, update (or create!) the documentation
3. Ensure the tests pass
4. Make sure that your code lints and that you've followed our coding style
5. Write a title and, if necessary, a description of your work suitable for publishing in our release notes
6. Mention any related issues in this repository (as #ISSUE) and in other repositories (as kobotoolbox/other#ISSUE)
7. Open an issue in the docs if there are UI/UX changes

Description

Enable the creation of access logs when users are authenticated.

Notes

Adds a method to the AuditLog class to create from a request, with logic to handle regular logins, non-persisted authenticated requests, and logins via django-loginas. This is meant to be called from a user_logged_in signal handler, which passes the request along, or an authentication class. Technically it can be called with any request but it will only log the authentication of the user, not any action they performed.

For any request, it will store the ip, OS, and browser of the request (taken from the headers) as well as information about the user in request.user. The user id is also stored as the object_id, with the object_type being the name of the user model.

If the url_name of the resolver is 'loginas-user-login,' we also store information about the _cached_user, which represents the user making the original request. This should work even in the case of cURL requests since they require a CSRF token and session id, so the original user gets fully authenticated.

The authorization type can be set by the caller, otherwise it will default to 'django-loginas' if it's a loginas request and the name of the authenticating backend if it's a normal login request.

Related issues

Blocked by #5035 and #5044

[notion-workspace]

Capture all authentication events

[rgraber]

Closed in favor of #5055