Improve display of stack traces when exceptions happens in an extension interface

### Description

Currently we rely on native C# exception traces when errors happen inside a user implemented interface (validation/dataProcessing/appOptions). Application developers probably expect an explicit message informing them of both the class name and the interface used.

We should probably set up a `try--catch` block around these hooks, to add a message with the stack trace so that it is easier to identify the cause of the error.

### Additional Information

_No response_

Start by locating the validation, dataProcessing, and appOptions extension hooks; review how exceptions currently surface through native C# traces. Done means failures identify both the implementing class and interface while preserving stack-trace context, with coverage for each hook.

Written by the indexing model from the issue text.