Fix: handle pagination in ssm describeInstanceInformation & API Rate Limit

[ThaSami]

What this PR does / why we need it:

This PR fixes an issue where experiments running SSM by tag sometimes report misleading IAM permission errors. The root cause is twofold:

1. The implementation of DescribeInstanceInformation did not handle pagination properly. By default, the API returns limited results per page, so if target instances reside on subsequent pages, they won't be found in the first API response—resulting in erroneous permission error messages.

2. The code was not properly handling AWS API rate limits, causing failures during high-volume operations when throttling occurred.

The fix:

• Updates the code to use DescribeInstanceInformationPages to properly iterate through all pages and correctly aggregate instance information
• Implements exponential backoff with jitter when encountering AWS API rate limits

These changes ensure reliable operation even with large numbers of instances and during periods of high API load.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
fixes #737

Special notes for your reviewer:

Checklist:

• Fixes #
• PR messages has document related information
• Labelled this PR & related issue with breaking-changes tag
• PR messages has breaking changes related information
• Labelled this PR & related issue with requires-upgrade tag
• PR messages has upgrade related information
• Commit has unit tests
• Commit has integration tests
• E2E run Required for the changes

[neelanjan00]

Tagging @uditgaurav for a codeowner review.

[oba11]

Thank you @ThaSami for this PR. Alot of other folks will benefit from this, I'm looking forward to it getting merged by the litmus maintainers soon 🚀