Fix Java naming convention violations for variables and methods

[Copilot]

Overview

This PR fixes Java naming convention violations in variables and methods throughout the codebase to improve code quality and consistency with Java best practices.

Problem

Several instance variables and method names were using ALL_CAPS naming convention, which in Java is reserved exclusively for static final constants. According to Oracle's Java Code Conventions, instance variables and methods should use camelCase naming.

Issues Found

1. Instance variables using ALL_CAPS instead of camelCase:

   • XID, DEFAULT_XID - should use camelCase since they are instance fields, not constants
   • LOGGER - instance logger fields should use camelCase naming

2. Method names with ALL_CAPS acronyms:

   • assertXIDNotNull(), assertXIDNull() - acronyms in method names should follow camelCase convention (only first letter capitalized)

Changes

Instance Variables

• XID → xid in test classes (GrpcTest, GlobalBeginResponseTest)
• DEFAULT_XID → defaultXid in RootContextTest
• LOGGER → logger in BaseUndoLogParserTest and TccHookTest

Methods

• assertXIDNotNull() → assertXidNotNull() in DefaultGlobalTransaction
• assertXIDNull() → assertXidNull() in DefaultGlobalTransaction

Files Modified

• core/src/test/java/org/apache/seata/core/context/RootContextTest.java
• core/src/test/java/org/apache/seata/core/protocol/transaction/GlobalBeginResponseTest.java
• integration/grpc/src/test/java/org/apache/seata/integration/grpc/interceptor/GrpcTest.java
• rm-datasource/src/test/java/org/apache/seata/rm/datasource/undo/BaseUndoLogParserTest.java
• tcc/src/test/java/org/apache/seata/rm/tcc/TccHookTest.java
• tm/src/main/java/org/apache/seata/tm/api/DefaultGlobalTransaction.java

Testing

All affected tests have been run and pass successfully:

• RootContextTest: 16 tests ✅
• GlobalBeginResponseTest: 3 tests ✅
• GrpcTest and related: 12 tests ✅
• DefaultGlobalTransactionTest: 4 tests ✅
• UndoLogParser tests: 27 tests ✅
• TccHookTest: 9 tests ✅

Impact

• No functional changes - only naming improvements
• Improved code quality - follows Java naming conventions
• Better maintainability - consistent naming throughout codebase
• Zero breaking changes - all changes are internal to test and implementation files

---

This change aligns with the issue requirement: "检测不符合Java规范，不符合上下文语义的变量并优化它" (Detect variables that do not conform to Java specifications and context semantics and optimize them).

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• httpbin.org
• registry.npmmirror.com
  • Triggering command: npm install (dns block)
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)
• repository.apache.org
• seata.io
• www.apache.org

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

检测不符合Java规范，不符合上下文语义的变量并优化它。

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.