Refactor Machine Deletion Logic in Integration Tests

[so-sahu]

Description

The current machine deletion logic in integration tests is causing multiple unnecessary calls to the libvirt-provider and flooding of logs in the console as seen here. This is because the machine deletion is called inside the Eventually block, as seen in this example.

Proposed Solution

Refactor the machine deletion logic in integration tests to avoid unnecessary calls and log flooding.

Expected Behavior

Machine deletion logic should be optimized to avoid multiple unnecessary calls and log flooding.

Additional Context

This enhancement will improve the efficiency and performance of integration tests by optimizing the machine deletion logic.