Trigger fatalErrorHandler for PEAR errors and for logs with severity ERROR or higher

[mattwire]

Overview

@mlutfy This allows extensions like reporterror to report most errors in CiviCRM. It includes your patch from https://lab.civicrm.org/extensions/reporterror/-/blob/master/README.md

Before

Only CRM_Core_Error::fatal() errors handled by fatalErrorHandler.

After

CRM_Core_Error::fatal(), PEAR error and \Civi::log()->error (and higher) triggers fatalErrorHandler.

Technical Details

Comments

If you don't have an extension installed which implements $config->fatalErrorHandler this PR has no effect. If you do have an extension installed then it can react to all(?) errors triggered by CiviCRM.

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[seamuslee001]

Change looks fine to me and shouldn't impact anything and tests have passed merging

[MegaphoneJon]

This PR causes CiviMail to crash in its most common configuration on any unknown email address; see https://lab.civicrm.org/dev/mail/-/issues/72.