Adding additional wait to avoid eventual consistency issues

[RanVaknin]

Motivation and Context

The Kinesis stability test is failing often with the following error:

ResourceInUseException: Stream kinesisstabilitytest1743709690580 under account 990724664260 not ACTIVE or UPDATING, instead in state CREATING

This is despite the fact we are using a waiter that is supposed to verify that the stream is active before operating on it.
Adding logs reveals an eventual consistency issue with Kinesis where the stream state has no propagated server side and causes this exception:

Checking stream status at 3764ms
Current stream status: ACTIVE at 3850ms
Stream kinesisstabilitytest1743709690580 is now ACTIVE after 3851ms
ResourceInUseException: Stream kinesisstabilitytest1743709690580 under account 990724664260 not ACTIVE or UPDATING, instead in state CREATING

@joviegas has run in the same problem with the KinesisintegTest, so I borrowed his solution and it seems to have fixed the problem. #5949

Testing

Running this test with a @RepeatedTest(20) and observed a 25% failure rate. After adding the additional waiting I see a 0% failure rate.

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud