Catch Throwable instead of Exception will also catch NULL issues
Problem/Motivation
In some critical code areas like e.g. \Drupal\eca\Entity\Objects\EcaAction::execute we use 'try/catch' for \Exception. This will still fail with a WSOD if an access check or execution of an action wants to do something on a NULL object. See #3331855: Smart Date - "Set field value" AssertionError as an example.
Proposed resolution
Catching \Throwable instead will also catch these issues and provide a much safer experience, especially while building models where it is happing a lot, that e.g. wrong field names get used in ECA configuration.
There are other places too like e.g. collecting all available plugins where this would help a lot to avoid issues with incompatible modules.
Edited by drupalbot