Attachments with path too long lead to missing results in trx

[kaadhina]

If there are test cases with attachments with path too long, it can lead to missing results. in trx report. We may skip the attachment but this should ideally not lead to missing test results in the trx

This has more detailed info and logs:
https://developercommunity.visualstudio.com/content/problem/612228/azure-devops-unit-test-result-not-being-published.html

AB#1865106

[nohwnd]

Adding sprint because it looks like low hanging fruit for some future sprint.

[nohwnd]

Not clear to me how the linked issue is connected to long paths, if you are still around @kaadhina and you remember what was going on, can you tell me?