fix: posting logs to OpenAEV expects a response but does nothing with it

[antoinemzs]

Description

The posting of logs to OpenAEV (so that OpenAEV is aware of the output of various integrations) expects that OpenAEV returns some JSON, but discards it right away.

xtm-composer/src/api/openaev/connector/post_logs.rs

Lines 21 to 25 in c9261b5

	// Discard the result
	let _ = handle_api_response::<JSON>(
	add_logs_response,
	"push logs for connector instance"
	).await;

It's perhaps a mistake. OpenAEV does not return a body for this POST as per the API spec, so XTM Composer errors instead when trying to parse (and discard) the response.

XTM Composer should be changed to not expect a body and therefore not error in the absence of one.

Environment

All latst software as of writing

Reproducible Steps

Steps to create the smallest reproducible scenario:

1. Deploy an integration through the OpenAEV catalog
2. Wait for a while as the integration produces output and that this output is POSTed to OpenAEV
3. Error in the XTM Composer own logs

Expected Output

No error

Actual Output

Error

Configuration

# config/default.yaml or relevant configuration

Logs

{"timestamp":"2026-05-06T11:41:32.358074Z","level":"ERROR","fields":{"message":"Failed to parse JSON for push logs for connector instance: error decoding response body"},"target":"xtm_composer::api::openaev::api_handler"}

Additional information

Screenshots (optional)