[Bug] Change GenericExceptionOnRun to have node_info

[dbeatty10]

Is this a new bug in dbt-core?

• I believe this is a new bug in dbt-core
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

If a "generic" error occurs in a call runner (such as a Python keyword error), the "GenericExceptionOnRun" logging event is issued, but doesn't have node_info in it. All call runners have a node associated with them, so we should add node_info to events that are issued in the call runner code path.

Expected Behavior

The GenericExceptionOnRun logging event should have node_info.

Steps To Reproduce

Generally in order to see this, you would have to have a Python error. This happened for a pre-release version of the unit testing feature, but is hard to reproduce in a test case since you'd have to force a Python error.

Relevant log output

The lack of GenericExceptionOnRun in the node associated logs in the IDE.

Environment

- OS:
- Python:
- dbt:

Additional Context

Internal slack thread: https://dbt-labs.slack.com/archives/C012TTNN0JK/p1707407183148229

@gshank said that the solution might be:

for this particular case we could change GenericExceptionOnRun to have node_info since it's thrown in a call runner