Settings forms: friendly error messages instead of raw codes

Severity: Medium Area: Admin settings

Org and project settings forms surface raw res.error values (e.g. failed, upgrade_required, Postgres messages).

Not user-friendly compared to doc feedback's friendlyError() pattern elsewhere in the app.

Fix: Map known error codes to plain-language messages in settings forms.