fix(engine): reject Iterator take/drop limits above 2^53 - 1

[IamYipi]

This Pull Request implements the limit validation that tc39/ecma262#3776 added to Iterator.prototype.take and Iterator.prototype.drop.

It changes the following:

• Adds the new step 7 to both methods. When limit converts to a finite Number greater than 2^53 - 1, the method closes the underlying iterator and throws a RangeError. Infinity is still accepted. NaN and negative limits are rejected as before.
• Renumbers the step comments after the new step.
• Adds unit tests for limits above Number.MAX_SAFE_INTEGER, equal to it, and Infinity. They also check that a rejected limit closes the underlying iterator.

Test262 results for the full suite, compared with main using boa_tester compare: 6 tests fixed, no regressions.

test/built-ins/Iterator/prototype/take/limit-rangeerror.js
test/built-ins/Iterator/prototype/take/argument-effect-order.js
test/built-ins/Iterator/prototype/take/argument-validation-failure-closes-underlying.js
test/built-ins/Iterator/prototype/drop/limit-rangeerror.js
test/built-ins/Iterator/prototype/drop/argument-effect-order.js
test/built-ins/Iterator/prototype/drop/argument-validation-failure-closes-underlying.js

cargo fmt --all --check is clean. So is cargo clippy -p boa_engine --all-features --all-targets with -D warnings.