When unit test contains a crash, xcresulttool report generation will error

[amleszk]

Hello thank you for creating this useful tool.

We observed an error generating reports when crash has occurred in one of the unit tests. It might be due to the crash log message containing a stack trace, not being filtered in the report. And causing the text size to be bloated.

Steps to reproduce

• Add fatalError("Crash") into a XCTestCase
• Run Action [xcresulttool](https://github.com/kishikawakatsumi/xcresulttool)
• Tool fails with large report issues and other errors

Warning: The 'summary' will be truncated because the character limit (65535) exceeded.
Error: Invalid request.

For 'properties/message', {"_value"=>{}} is not a string.
For 'properties/message', {"_value"=>{}} is not a string.
For 'properties/message', {"_value"=>{}} is not a string.
For 'properties/message', {"_value"=>{}} is not a string.
For 'properties/message', {"_value"=>{}} is not a string.
Error: $GITHUB_STEP_SUMMARY upload aborted, supports content up to a size of 1024k, got 1841k. For more information see: https://docs.github.com/actions/using-workflows/workflow-commands-for-github-actions#adding-a-markdown-summary