[ws-manager-mk2] Fix stopped status

[WVerlaek]

Description

Fixes the first reconciliation of a workspace setting its phase to Stopped briefly, because there are 0 pods and no ContentReady condition, so isDisposalFinished() was returning true. Now only check for isDisposalFinished if in a Stopping state, so we don't transition to Stopped for a tick after workspace creation

Related Issue(s)

Part of #11416

How to test

Run unit tests, or create a workspace and observe the debug logs from the controller not setting the workspace status to Stopped in the first reconciliation

Release Notes

NONE

Documentation

Build Options:

• /werft with-github-actions
  Experimental feature to run the build with GitHub Actions (and not in Werft).
• leeway-no-cache
  leeway-target=components:all
• /werft no-test
  Run Leeway with --dont-test

Publish Options

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer Options

• with-ee-license
• with-slow-database
• with-dedicated-emulation
• with-ws-manager-mk2
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment Options:

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• /werft with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

[WVerlaek]

/unhold