Bug: using the default processor middleware in the processor template causes an error

[maha-mstfa]

Bug description

if you write your processor using the processor template, it uses sdk.ProcessorWithMiddleware(&Processor{}, sdk.DefaultProcessorMiddleware()...) in the NewProcessor method.
after building the processor using make build and adding it to a processors directory, and running conduit, you get this:

2025-01-23T13:10:50+00:00 WRN processor teardown failed error="processor plugin stopped while trying to send command *processorv1.CommandRequest_Teardown: plugin is not running\nmodule closed with exit_code(2)" component=plugin.processor.standalone.Registry stack=null
2025-01-23T13:10:50+00:00 WRN could not load standalone processor plugin error="processor plugin stopped while waiting for response to command *processorv1.CommandRequest_Specify: plugin is not running" component=plugin.processor.standalone.Registry plugin_path=/Users/mahahajja/repos/conduit/processors/conduit-processor-hl7.wasm stack=[{"file":"/Users/mahahajja/repos/conduit/pkg/plugin/processor/standalone/processor.go","func":"github.com/conduitio/conduit/pkg/plugin/processor/standalone.(*wasmProcessor).executeCommand","line":347},{"file":"/Users/mahahajja/repos/conduit/pkg/plugin/errors.go","func":"github.com/conduitio/conduit/pkg/plugin.init","line":23}]

Steps to reproduce

1. use the processor template repo
2. write a filler processor
3. run make build
4. add the wasm processor to a processors directory
5. run conduit

Version

v0.4.0

[hariso]

This PR fixes the issue: ConduitIO/conduit-processor-template#22. And here are 2 PRs that improve logging so that we can more easily troubleshoot this in the future: #131 and ConduitIO/conduit#2241.