[14.0] l10n nl xaf audit file export reliability

[NL66278]

Add more code to prevent server crashes and other problems due to auditfile export

[thomaspaulb]

@NL66278 For clarity to other reviewers, could you edit the description of this issue and add a checkboxed list of PR's that you are forward-porting with this PR?

Also, could you remove the first commit, because that one is already part of another PR.

[NL66278]

@thomaspaulb When the other PR's are merged, I could rebase this one. Or alternatively when this one is approved we can have all the improvements in one go.

[ntsirintanis]

Code review

[github-actions]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

[hbrunn]

it's unclear to me which problem this solves.

Then we have a database at hand which is very much specialized in locking things, so the correct way to prevent parallel execution would be something like

cr.execute(select id from xaf_auditfile_export where id=%s for update', (this.id,))

instead of some home brewed mechanism.

I like keeping failed auditfiles, but instead of a success flag I'd prefer introducing a state field [draft, done, fail] to be in line with other exports from this repo, like the vat export.

Finally, illegal characters should be fixed with a specialized widget for text output