[Tushar15769]

This PR fixes an issue in array-rest destructuring where next() could be called again even after the iterator was already marked as done.

The problem occurs when earlier elements in the destructuring pattern have already exhausted the iterator. When processing the rest element, iterator_to_array was still calling iterator_next() without checking the iterator's completion state first.

The change adds a completion check before requesting the next iterator result. The existing check after iterator_next() is kept to handle normal iterator exhaustion.

It also adds tests covering the following cases:

• An iterator that immediately returns done: true.
• An iterator that yields multiple values before finishing.
• An exception thrown from next().
• Normal array-rest destructuring.
• An iterator exhausted by preceding elements in the destructuring pattern.

The changes are limited to iterator.rs and iterators.rs. No changes were made to the other bugs mentioned in the issue.

Tests run:

• cargo fmt --all -- --check
• cargo test -p boa_engine --lib
• cargo test -p boa_engine --lib -- tests::spread
• cargo test --workspace

Fixes #5648