Wrong package state calculation for aborted deployments

Issue

Aborting a cf push results in wrong package_state being calculated.

Steps to Reproduce

• push a simple app (e.g. [1])
• re-push and abort (CTRL+C) during staging phase (Staging app and tracing logs...)

Expected result

• cf curl "/v2/apps/:guid" shows "package_state": "STAGED"

Current result

• cf curl "/v2/apps/:guid" shows "package_state": "PENDING"

Context

The package_state method in ProcessModel [2] uses the PackageStateCalculator [3] which assumes that for a STAGED package the desired droplet must equal the latest droplet [4]; for an aborted push this assumption is wrong.

[1] https://github.com/cloudfoundry-samples/test-app
[2] https://github.com/cloudfoundry/cloud_controller_ng/blob/932817c66ffa3c6ed1f819cd77eda7013d59afd6/app/models/runtime/process_model.rb#L197-L200
[3] https://github.com/cloudfoundry/cloud_controller_ng/blob/main/app/models/runtime/helpers/package_state_calculator.rb
[4] https://github.com/cloudfoundry/cloud_controller_ng/blob/932817c66ffa3c6ed1f819cd77eda7013d59afd6/app/models/runtime/helpers/package_state_calculator.rb#L35

Start with app/models/runtime/process_model.rb and app/models/runtime/helpers/package_state_calculator.rb, then trace how package_state is calculated after an aborted cf push. Reproduce the staging interruption and check cf curl "/v2/apps/:guid". Done means an aborted push reports package_state as STAGED rather than PENDING.