feat(settings): Introduce TaskProcessingSuccessRate setup check

[marcelklehr]

Summary

Currently, it can happen that AI tasks fail without the admin realizing that they misconfigured their instance. This setup check makes the admin aware about potential issues with the AI apps.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

[provokateurin]

Shouldn't there be logs somewhere, which they already monitor anyway?

[marcelklehr]

Shouldn't there be logs somewhere, which they already monitor anyway?

Normal processing errors are logged as warning, only unexpected errors are logged as errors. We could also raise the log level of normal errors to error. I'm uncertain if that's a good idea, as normal errors can sometimes be caused by users and thus wouldn't be a real setup issue.

[provokateurin]

Every error is "unexpected" and not "normal", so I don't get the distinction here 🤔