feat: improve observation validation for POST requests

[arielsepton]

Description

This PR modifies the isObjectValidForObservation function to improve the handling of POST requests. Previously, the validation relied on the presence of a non-empty response body. However, some APIs (e.g., the one mentioned in the related issue) return an empty body on successful creation, leading to incorrect behavior where the provider attempts repeated creation attempts.

The updated logic now checks for a non-zero StatusCode, ensuring that valid responses are not incorrectly excluded from observation.

Why is this change needed?

The existing logic fails for APIs that respond with an empty body on successful creation (e.g., HTTP 201). This causes unnecessary retries and results in conflicts (HTTP 409). By updating the validation logic, we ensure proper handling of such cases.

Changes Made

• Updated the isObjectValidForObservation function:
  • Changed the check from cr.Status.Response.Body != "" to cr.Status.Response.StatusCode != 0.
  • This ensures that the validation focuses on the status code rather than the presence of a body.
• Updated the related unit tests.

Related Issues

Resolves: #68