gh-148285: Allow recording uops after specializing uops

[adityakrmishra]

• Fixes Allow recording uops after specializing uops #148285
• Replaces closed PR gh-148285: Allow recording uops after specializing uops #148367

The Issue:
Currently, analyzer.py forces any uop with records_value == True to be at index 0. This prevents Tier 2 recording uops from safely trailing Tier 1 specializing uops.

The Fix (V2):
Following feedback from @Sacul0457 on the previous PR, simply checking if the preceding uop was tier == 1 was too permissive (it allowed recording uops to follow any Tier 1 uop, not just specializing ones).

This updated patch uses a strict positional uop_index tracker in add_macro().
A recording uop is now only permitted if:

1. It is at uop_index == 0 (the very first uop).
2. OR it is at uop_index == 1 AND the preceding uop's name explicitly starts with _SPECIALIZE_.

CacheEffect (e.g., unused/1) and flush parts do not increment the uop_index, ensuring they remain completely transparent.

This strictly enforces the architecture while allowing structures like:
macro(X) = _SPECIALIZE_X + _RECORD_TOS_TYPE + unused/1 + _X;

• Issue: Allow recording uops after specializing uops #148285

[bedevere-app]

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.