[FEATURE] Stop preventing Kyma updates depending on the status

[sdischer-sap]

Context
The provider currently does only attempt updating the kyma environement in case the instance is in an ok state as identified via the state attribute returned from the API. Since this state reflects the last status update there are scenarios in which an instance stays in the UPDATING state forever, thus preventing any further updates.

Scope
Provided that the API always returns the latest state of data there is not really a point in preventing those updates. The precondition to this is that the API immediately returns the updated data after the update has been send. If the old data is returned while the changes are still applied (which sometimes can take a couple of minutes) this change might not be so easy. So this needs to be verified as part of this ticket.

Acceptance criteria

• provider ignores the state for detecting drifts
• provider only does one update for change (otherwise we need to rethink this issue)

Workarounds & Alternatives
Unstuck kyma instance by applying an empty update in the cockpit (this is not always even possible)

Additional context
This issue came up a lot during our attempts to fix continuous updates for stakeholders.

[sdischer-sap]

@GenosseOtt good to go to refinement once you approve.