If the plugin is called via go run (like in the tests), this command adds an implicit error status line, which
must be handled in the plugin adapter to find the correct error json.
The plugin might provide error output. This error output must be separated from the formal error status
As long as we don't have a formal way to get to the stderr stream from the context, the error output is added
to the error message
What this PR does / why we need it:
go run(like in the tests), this command adds an implicit error status line, which must be handled in the plugin adapter to find the correct error json.Which issue(s) this PR fixes: