Simplify the reasons used in status conditions to only Succeeded and Failed

[everettraven]

Currently, we have a mixture of reasons used for different status condition types that are a flavor of the terms Succeeded or Failed.

For example, we have:

• UnpackSuccess and UnpackFailed for the Unpacked condition type
• Success and InstallationFailed for the Installed condition type
• Success and ResolutionFailed for the Resolved condition type

As outlined in the v1 API Review RFC, we should simplify this to using Succeeded and Failed for all the status condition types (Unpacked, Installed, Resolved) to ensure consistency.

[bentito]

Can you give some more detail? Should we refer back to the RFC that is related?: https://docs.google.com/document/d/1JWJxnDXM0X1JQ67ZIDx5j1ayb1d7ajrK_uSDDaz0G98

[everettraven]

@bentito I just updated the description. I created this issue as part of the v1 API review epic task list late yesterday and hadn't had a chance to finish going through and populating the issue descriptions until now :)