Fix tiny_map from_iter where one operation was being dropped

[Thor-Bjorgvinsson]

Motivation and Context

15th operation was being dropped when iterator was being read into a TinyMap

Description

The 15th operation was being dropped when the if statement was caught because the operation had been popped of the iterator but hadn't been added to the vec of operations before the two iterators were being chained and collected into a

Testing

Added unit tests that reproduced the issue and verified that the issue is fixed

Checklist

• I have updated CHANGELOG.next.toml if I made changes to the smithy-rs codegen or runtime crates
• I have updated CHANGELOG.next.toml if I made changes to the AWS SDK, generated SDK code, or SDK runtime crates

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[david-perez]

Thanks!

[82marbag]

@Thor-Bjorgvinsson you have probably ticked the wrong box in the checklist

[david-perez]

@Velfi Seems like these tests are flaky. Although it's the first time I've seen them fail.

running 4 tests
test test_smol_runtime_timeouts ... FAILED
test test_async_std_runtime_timeouts ... FAILED
test test_smol_runtime_retry ... ok
test test_async_std_runtime_retry ... ok

failures:

---- test_smol_runtime_timeouts stdout ----
thread 'test_smol_runtime_timeouts' panicked at 'actual = 769.061231ms, expected = 350ms', sdk/s3/tests/alternative-async-runtime.rs:128:5

---- test_async_std_runtime_timeouts stdout ----
thread 'test_async_std_runtime_timeouts' panicked at 'actual = 778.09071ms, expected = 350ms', sdk/s3/tests/alternative-async-runtime.rs:128:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    test_async_std_runtime_timeouts
    test_smol_runtime_timeouts

test result: FAILED. 2 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 1.60s