test: strengthen IP address utility assertions

[Loyal-Young]

Summary

• replace JVM assert statements in IPAddressUtilsTest with AssertJ assertions
• preserve all IPv4, IPv6, CIDR, scope, and bracketed-address expectations

Why

Framework assertions make each test expectation explicit and provide useful failure diagnostics without depending on JVM assertion settings.

Impact

Production code is unchanged. The existing IP address utility coverage becomes more robust and easier to diagnose when it fails.

Validation

• git diff --check
• mvn --batch-mode --no-transfer-progress -pl common -Djacoco.skip=true -Dtest=IPAddressUtilsTest test

[RockteMQ-AI]

Review by github-manager-bot

Summary

Replaces JVM assert statements with AssertJ assertions in IPAddressUtilsTest, making test expectations explicit and independent of JVM assertion settings. Clean, well-scoped test improvement.

Findings

• [Info] The diff rewrites the entire file (+84/-83 on a 92-line file), which suggests a line-ending normalization (CRLF → LF) alongside the semantic changes. Consider mentioning this in the PR description or separating it into a dedicated commit to keep git blame history cleaner.
• [Info] Also fixes the missing newline at end of file — good cleanup.

Assessment

• All existing test expectations (IPv4, IPv6, CIDR, scope, bracketed-address) are correctly preserved
• assertThat(X).isTrue() / assertThat(X).isFalse() conversions are semantically identical to the original assert X / assert !X
• AssertJ import is correctly added
• No production code changes

LGTM. Straightforward test hardening with no risk.

---

Automated review by github-manager-bot