[13.x] Prevent fatal errors when logging deprecations fails

[GrahamCampbell]

The prefer-lowest builds on 13.x are currently failing because PHP 8.4 raises an implicit-nullable deprecation while compiling Monolog 3.4's Logger class. The deprecation handler then attempts to log through Monolog while that class is still mid-autoload, and the process fatals with a "Class Monolog\Logger not found" error. This is what kills the Concurrency child processes on Linux and the ExceptionHandler subprocess on Windows. Reporting a deprecation should never be able to crash the application, so the logging attempt now ignores any failure that occurs while building or using the deprecations channel.

[shaedrich]

You may shorten this to the following and reduce the cognitive load if you want:

Suggested change

	with($logger->channel('deprecations'), function ($log) use ($message, $file, $line, $level, $options) {
	if ($options['trace'] ?? false) {
	$log->warning((string) new ErrorException($message, 0, $level, $file, $line));
	} else {
	$log->warning(sprintf('%s in %s on line %s',
	$message, $file, $line
	));
	}
	});
	with(
	$logger->channel('deprecations'),
	fn ($log) => $log->warning(($options['trace'] ?? false)
	? (string) new ErrorException($message, 0, $level, $file, $line),
	: sprintf('%s in %s on line %s', $message, $file, $line),
	),
	);

[GrahamCampbell]

I think that's a worse refactor tbh. This is an abuse of expressions for something that should be a statement.