Formatting of CMOR errors is broken

[schlunma]

#1296 introduced a new formatting of CMOR errors which appears to be broken, e.g.,

esmvalcore.cmor.check.CMORCheckError: Coordinate plevs has var name plev7 instead of plevThere were errors in variable clisccp:
 tau: standard_name should be atmosphere_optical_thickness_due_to_cloud, not NoneThere were errors in variable clisccp:
 clisccp: does not match coordinate rank

It looks like only the error messages are affected (I think a comma is missing), but it might be good to also check warnings and debug messages.

ESMValCore/esmvalcore/cmor/check.py

Lines 233 to 242 in 882224c

	if self.has_errors():
	msg = '\n'.join([
	f'There were errors in variable {self._cube.var_name}:'
	'\n '.join(self._errors),
	'in cube:',
	f'{self._cube}',
	'loaded from file ' +
	self._cube.attributes.get('source_file', ''),
	])
	raise CMORCheckError(msg)

It would be great to fix this before the release.