[code-reflection] Integrated: Remove op name state from Op

[Paul Sandoz]

On Thu, 18 Sep 2025 23:54:49 GMT, Paul Sandoz <psandoz at openjdk.org> wrote:

> The operation's name should only be used for writing to and parsing from text, or more generally when externalizing the operation. Otherwise, it should not generally be relied upon since the class itself should be sufficient (although there currently are a few areas, namely the interpreter that should be updated in a separate PR to remove its dependence on that).
> 
> - `Op` no longer has an instance field holding the operation name
> - `Op.opName` is named to `Op.externalizeOpName`
> - By default the method `Op.externalizeOpName` returns `this.getClass().getName()`, which may be overridden.
> 
> Also cleaned up `Op`, making more methods final and grouping methods more appropriately.

This pull request has now been integrated.

Changeset: b5b2a61e
Author:    Paul Sandoz <psandoz at openjdk.org>
URL:       https://git.openjdk.org/babylon/commit/b5b2a61e3d5b56f2fcfcc377a4515cc88f323df4
Stats:     539 lines in 34 files changed: 194 ins; 90 del; 255 mod

Remove op name state from Op

Reviewed-by: mcimadamore

-------------

PR: https://git.openjdk.org/babylon/pull/577