Increase number of items in `.status.history` to five

[matheuscscp]

Currently we truncate to only two elements. This feature was originally designed to support the controller state machine, but it can also be about observability. We should evaluate if it's feasible increasing from two to five elements without affecting the state machine logic.

Note: When using RetryOnFailure the amount is already five, since the retry state machine for this setting is much simpler. We should, however, review one more time if this is really OK and fix any potential bugs this could be causing to the action state machine.

[Iam-Karan-Suresh]

Hi @matheuscscp ,

I’ve been looking into this issue and wanted to confirm my understanding.

Currently, Snapshots.Truncate() truncates the history after the first previous deployed or superseded snapshot. In most cases this results in keeping only two entries (the latest snapshot and the first previous deployed/superseded one). The defaultMaxHistory = 5 fallback only applies when no deployed/superseded snapshot exists.

Meanwhile, TruncateIgnoringPreviousSnapshots() (used in the RetryOnFailure path) already keeps up to five snapshots, which provides better observability.

My understanding is that we could modify Truncate() to retain up to defaultMaxHistory entries while still ensuring that the previous deployed/superseded snapshot is always included. Since Latest() and Previous() rely on index-based lookups rather than a fixed history length, this change should not affect the state machine logic.

If this approach sounds reasonable, I’d be happy to work on implementing the change and updating the related tests.

Please let me know if I can take this issue.