Editorial: Update range comparisons involving a zero

[gibson042]

• When zero bounds a Number range, always use < -0𝔽 or > +0𝔽 (there was one exception).
• Consolidate static bounds checking in IsValidIntegerIndex and StringGetOwnProperty (index Numbers with negative sign bit are in the same "not applicable" category as non-integers).
• Clean up StringGetOwnProperty to remove a redundant check and swap comparison operands for a more conventional ordering.

[bakkot]

I am pretty sure this is indeed editorial, but I'd like @syg to confirm. (Specifically, this change means that passing -1 will now skip the MakeTypedArrayWithBufferWitnessRecord step, but per the note about bounds checking not being a synchronizing operation I think that's not observable.)

[syg]

Yeah, I think because it's unordered it is fine.

[bakkot]

LGTM pending approval from Shu for the TA change. The esmeta failures can be fixed by removing TypedArrayGetElement and TypedArraySetElement from esmeta-ignore.json, per the CI logs, which we can do when merging if you don't get there first.