Structured header for a redefinition should support identifying the clause being superseded

The boilerplate for an operation that supersedes another of identical name (generally ECMA-402 updating ECMA-262) is something like This definition supersedes the definition provided in <emu-xref href="#sec-…"></emu-xref>. (cf. ECMA-402 and Temporal). It would be great if the redefinition key supported not just true but rather an identification of the clause being superseded to be used as a source for generating such boilerplate, or failing that if a sibling key specified the same information (although that seems less useful because a redefinition should always be covering something).

But note that pursuing this path should also invert the suppression logic—the aoid should be assigned to and inbound links should reference the operation identified as a redefinition rather than the operation being superseded. But having written that, it seems beneficial anyway.

Start by reading the structured headers documentation linked in the issue and compare the ECMA-402 and Temporal examples. Trace how the redefinition key currently affects boilerplate, aoid assignment, and inbound links; done means the superseded clause can be identified and the generated references and suppression behavior follow the proposed inversion.