update audit-log presets

[sjvans]

re #1443

[renejeglinsky]

How about using this format instead of the code block?

[grenik]

@renejeglinsky thanks for fixing it, but I think there are two open points left:

1. I think Fix outdated audit logging config (#1442) #1443 (comment) from @sjvans regarding default outboxed was not reflected (it's not false anymore)

2. I thought kind is the new level of abstraction from the internal implementation, which is there exactly to avoid such errors (plugin impl changed > config doesn't work anymore > documentation must be changed / code throws errors)
   See the audit logging plugin impl
   This is why I suggested to replace impl with kind in Fix outdated audit logging config (#1442) #1443
   Is my understanding wrong?

[renejeglinsky]

Hi @grenik
for the latter: As this kind is the implicit default (as you can see from the source you linked or by executing cds env requires.audit-log), there's no need to list it here. That way, you'd not benefit from any changes done within the plugin. If you stick to the defaults, you benefit from all the changes there. At least that is my understanding. Maybe @sjvans can confirm or improve my answer.
Wrt your first point, thanks for catching this! I'll fix it.

[sjvans]

i'm a little torn on this one. i don't really see the value in [development]: { kind: 'audit-log-to-console' } without also listing what this predefined kind contains. but if we also add the three kinds, then the snippet gets way too long. that's why i actually kind of like the current state, because it reflects the effective env. but it really is confusing for the readers...

[sjvans]

maybe something like #1481?