OOM during StringBuilder in AssertionErrorMessagesAggregrator#aggregrateErrorMessages

Summary

Building the string for an assertAll can lead to an OOM, it would be better to return a truncated message if the error count is larger than some configurable number - or at least add a defensive check and/or catch OOM to produce a more useful outcome than

Java heap space
java.lang.OutOfMemoryError: 
	at java.util.Arrays.copyOf(Arrays.java:3332)
	at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124)
	at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:448)
	at java.lang.StringBuilder.append(StringBuilder.java:136)
	at org.assertj.core.error.AssertionErrorMessagesAggregrator.aggregrateErrorMessages(AssertionErrorMessagesAggregrator.java:25)
	at org.assertj.core.api.SoftAssertionError.<init>(SoftAssertionError.java:36)
	at org.assertj.core.error.AssertionErrorCreator.multipleSoftAssertionsError(AssertionErrorCreator.java:75)
	at org.assertj.core.api.SoftAssertions.assertAll(SoftAssertions.java:166)
	at com.redacted.testThing(Redacted.java:129)

This should be easy to repro.

Thanks for considering - I can submit a PR if that would help here.

從 AssertionErrorMessagesAggregrator.java:25 開始，追蹤 SoftAssertionError 和 SoftAssertions.assertAll 如何建構彙總訊息。使用足夠多的錯誤重現 assertAll 以觸發失敗，然後針對過大的訊息定義並驗證一種有界或其他防禦性的結果。