Add full CloudFormation stack event pagination to stack monitoring

[GrahamCampbell]

Summary

monitor-stack.js currently fetches only the first page of CloudFormation DescribeStackEvents during stack monitoring. The SDK v3 migration roadmap intentionally preserves that first-page behavior in PR 5 to avoid mixing behavior changes into the CloudFormation migration.

This issue tracks the follow-up UX enhancement to add full stack-event pagination after PR 5.

Current Behavior

lib/plugins/aws/lib/monitor-stack.js calls DescribeStackEvents once per polling cycle and processes only the returned StackEvents page.

For large or noisy stacks, relevant events may fall outside the first page returned by CloudFormation.

Desired Behavior

Stack monitoring should paginate DescribeStackEvents enough to reliably find and display relevant events for the current stack operation while preserving existing output semantics.

Scope

• Add full or operation-bounded DescribeStackEvents pagination to stack monitoring.
• Preserve current event ordering and duplicate suppression behavior.
• Preserve existing failure selection and error formatting behavior.
• Preserve delete-stack compatibility behavior for stacks that no longer exist.
• Keep SDK waiters out of this enhancement unless deliberately reviewed separately.

Acceptance Criteria

• Multi-page DescribeStackEvents responses are handled.
• Events are still logged once using loggedEventIds.
• Current operation boundary detection via the root stack *_IN_PROGRESS event remains correct when that event appears on a later page.
• Failure events on later pages are considered for stackLatestError.
• Completed-resource progress remains compatible with current behavior.
• Delete monitoring still treats the existing missing-stack case as delete-complete where appropriate.
• Unit tests cover multi-page event retrieval, duplicate suppression across pages/polls, failure event selection, and first-page compatibility.
• The SDK v3 CloudFormation migration remains behavior-preserving; this enhancement should be implemented separately from PR 5.

Background

The AWS SDK v3 migration roadmap resolves the post-PR 5 backlog decision by tracking this as a separate issue instead of implementing it during PR 5. PR 5 should preserve first-page stack monitor behavior while migrating CloudFormation calls to SDK v3.