Config rendering errors at the operation level can get swallowed by filter rules.

[jsoverson]

Describe the bug
Configuration failures for operation instances at the operation level don't get exposed to the user.

Expected behavior

If I have a busted config, I expect an error like everywhere else:

2023-06-27T15:00:36 ERROR interpreter:event_loop:event_loop:event{otel.name="tx_start" i=0 tx_id=7f6f2ccd-b23f-2abb-7b69-278e947c01c6}: tx_error=Component error: Could not render operation configuration: liquid: Unknown index
  with:
    variable=ctx.root_config
    requested index=token
    available indexes=

Actual behavior

No error, no warning, execution just continues as normal.

Environment:

• OS: mac
• Architecture: m1
• Build Version: HEAD

[jsoverson]

Fixed via #335