CLI crashes with panic if Microcks API returns unexpected responses

Nadie ha tomado este issue todavía.

While using the CLI, I noticed that pkg/connectors/microcks_client.go uses panic(err) in several places when reading HTTP response bodies or unmarshaling JSON.

If there is a temporary network glitch (e.g., the connection drops while reading the body) or if the Microcks server returns an invalid JSON response (like a 502 Bad Gateway HTML page from a proxy), the CLI will abruptly crash and print a Go stack trace instead of handling the error gracefully.

Additionally, methods like CreateTestResult use unsafe type assertions on the parsed JSON map (e.g., createTestResp["id"].(string)), which will also cause a panic if the id field is missing from the response payload.

Expected Behavior
The CLI should catch these errors, bubble them up through the standard error return values, and print a clean, user-friendly error message to the terminal before exiting with a non-zero status code.

Actual Behavior
The CLI completely crashes with a stack trace.

Suggested Fix
We should replace all instances of panic(err) in these client methods with proper context-wrapped errors (e.g., fmt.Errorf("failed to read response: %w", err)) since the functions already have an error return type defined. We should also add the comma-ok idiom to the type assertions to ensure we don't crash on missing fields.

Comienza en pkg/connectors/microcks_client.go revisando los métodos del cliente que leen los cuerpos de respuesta, deserializan JSON y usan la aserción de tipo id. Sustituye las rutas de fallo por errores devueltos y con contexto, y gestiona los campos de respuesta ausentes o no válidos; el trabajo estará terminado cuando los errores inesperados de red, JSON o de la forma de la respuesta lleguen a la CLI como fallos limpios con un código de salida distinto de cero, en lugar de un stack trace.

Escrito por el modelo de indexación a partir del texto del issue.