Fix broken auditlog browsing and auditlog more things

[jmbredal]

Auditlog did not display log entries properly. There were inconsitencies between getting data from context or api.

Changes done:

• Add log entries on crud of profiles
• Add log entries on crud of devices
• Add log entries when logging in and out

DataTable

• Use api only for data
• Add filters, sorting and searching
• Add DataTable to ipdevinfo (new tab)
• Fix DataTable for portadmin
• Fix DataTable main tool
• Add DataTable to user info (list and details)

[lunkwill42]

I think this still needs some fixing - adding a tasklist comment with my feedback

[lunkwill42]

This is my general feedback after giving this a quick look-over:

• I reloaded an auditlog page after switching to this branch, and got an error from /auditlog/actor/account/:

  Exception Type: TemplateDoesNotExist at /auditlog/actor/account/
  Exception Value: auditlog/logentry_list.html
  

  Not sure that this page is reachable any longer with your changes - in that case, urls.py and the defined views may need some pruning.

• I added a user to the Adminstrators group, and the auditlog reads "mvold added group NAV Administrators to foo". The grammar doesn't sound quite right: I didn't add a group to a user, I added the user to the group...

• There seems to be some inconsistensies in the verbs that are being used across NAV. Portadmin uses "verbs" with spaces separating multiple words, while other systems appear to use verbs with dashes separating words...

• We should maybe clean the UI: "Audit log" is two words in English, not one (and the camelcasing doesn't look pretty either)

• Audit log entries concering config changes to ports do not appear in the device's Audig log tab. Won't users find that strange?

• I'm not sure I like having the audit log tab in ipdevinfo at all, when I think about it. It makes it harder (given NAV's current auth system) to limit who is allowed to set audit logs. Can't the Audit log subsystem accept a netbox idenficator to filter in its URL, and then we can just link to this? It still requires one click.

• When changing SNMP communities, both the old and new values are logged in plaintext in the auditlog. We take care in most places to not print the communities unless you are editing them in SeedDB - should we not censor this?

• If we are audit logging changes to user objects, should we not also audit log changes to API tokens as well?

Some of these could very well be separate PRs, but we should discuss which one's we need to do something about before we merge this PR.

[jmbredal]

I consider the rest bigger tasks that we can do at a later time.

[lunkwill42]

Great. Added #1675, #1676 and #1677 for followup. Waiting for CI results before merging.