GH-131798: Allow the JIT to remove more int/float/str guards

[brandtbucher]

This changes the definitions of BINARY_OP_SUBSCR_LIST_INT, BINARY_OP_SUBSCR_STR_INT, BINARY_OP_SUBSCR_TUPLE_INT, and STORE_SUBSCR_LIST_INT to use our existing int/str guards for their operands (I'll add new guards for the containers themselves in a follow-up PR). This way, they can be removed when possible.

As part of this change, get rid of the _GUARD_BOTH_FLOAT, _GUARD_BOTH_INT, and _GUARD_BOTH_UNICODE micro-ops, since they just make the abstract interpreter more complicated for not much benefit.

• Issue: Better uop coverage in the JIT optimizer #131798

[brandtbucher]

As part of this change, get rid of the _GUARD_BOTH_FLOAT, _GUARD_BOTH_INT, and _GUARD_BOTH_UNICODE micro-ops, since they just make the abstract interpreter more complicated for not much benefit.

One nice unintended effect of this: x + x has only guards the type of x once now, rather than twice.

[brandtbucher]

Looks about 0.5% faster. According to the stats, this avoids:

• 34 million runtime float checks (~3% of the total)
• 695 million runtime str checks (~29% of the total)
• 3.344 billion runtime int checks (~38% of the total)