Fix/expunge historical version exception message

[patrick-werner]

Summary

Improve exception handling in the asynchronous Expunge job so that missing historical versions throw a clear, contextual error instead of HAPI‑2223: null.

Changes

In JpaResourceExpungeService.expungeHistoricalVersion(), replace orElseThrow(IllegalArgumentException::new) with a lambda that includes the missing version’s ID and partition in the exception message.

Update PartitionRunner’s error‑handling to extract cause.getMessage() and propagate it, ensuring the logged and thrown InternalErrorException carries the real root‑cause text.

Add a simple unit test to verify that an absent history entry yields a non‑null, descriptive exception message.

Related issue
Closes #6879

[Copilot]

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

hapi-fhir-storage/src/main/java/ca/uhn/fhir/jpa/dao/expunge/PartitionRunner.java:130

• [nitpick] Consider adding a separator (e.g., ': ') between Msg.code(1085) and cause.getMessage() to improve the clarity of the exception message.

throw new InternalErrorException(Msg.code(1085) + cause.getMessage(), cause);

[robogary]

Formatting check succeeded!