Improve error message for INVALID OPERATION opcode

[matkt]

PR description

This PR updates the behavior of the invalid operation opcode to return an error that includes the problematic opcode in the message, replacing the previous generic message.

Fixed Issue(s)

Thanks for sending a pull request! Have you done the following?

• Checked out our contribution guidelines?
• Considered documentation and added the doc-change-required label to this PR if updates are required.
• Considered the changelog and included an update if required.
• For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

• unit tests: ./gradlew build
• acceptance tests: ./gradlew acceptanceTest
• integration tests: ./gradlew integrationTest
• reference tests: ./gradlew ethereum:referenceTests:referenceTests

[matkt]

this is the evm specific PR @shemnon for #8129

[lu-pinto]

Instead of having the factory method here, move this ExceptionalHaltReason definition to its class, e.g.:

  static ExceptionalHaltReason newInvalidOperation(final long opcode) {
    return new ExceptionalHaltReason() {
      @Override
      public String name() {
        return INVALID_OPERATION.name();
      }

      @Override
      public String getDescription() {
        return "invalid opcode: 0x%02x".formatted(opcode);
      }

      @Override
      public String toString() {
        return name();
      }
    };
  }

And then call it like so here:

new OperationResult(0L, ExceptionalHaltReason.newInvalidOperation(getOpcode()));

[matkt]

not sure it's better but I don't have a strong opinion about that so I will do the change

[lu-pinto]

I think keeping all ExceptionHaltReason definitions in one place is best