[PLAT-8545] Capture the current thread name on crash

[kstenerud]

Goal

Capturing thread names is async-safe when getting the current thread name. This can be useful when recording Objective-C and C++ exceptions because they are handled on the same thread that threw the exception.

Note: This won't capture the offending thread name for mach exceptions because they are handled on the mach exception handler thread.

Testing

Added thread name checks for ObjC and C++ exception e2e tests.

[github-actions]

Bugsnag.framework binary size increased by 88 bytes from 814,568 to 814,656

    FILE SIZE        VM SIZE    
 --------------  -------------- 
  +0.1%    +132  +0.1%    +132    __TEXT,__text
  +1.1%     +32  +1.1%     +32    Binding Info
  +0.0%     +32  +0.0%     +32    String Table
  +0.0%     +16  +0.0%     +16    Symbol Table
  +0.8%     +16  +0.8%     +16    __TEXT,__const
  +2.4%      +8  +2.4%      +8    __DATA,__got
  +0.2%      +4  +0.2%      +4    Indirect Symbol Table
  -0.1%      -8  -0.1%      -8    [__DATA]
  [NEW]      +4  -1.8%     -84    [__LINKEDIT]
  -0.6%    -148  -0.6%    -148    [__TEXT]
  +0.0%     +88  [ = ]       0    TOTAL

Generated by 🚫 Danger

[nickdowell]

The changes to bsg_kscrw_i_writeThread LGTM but I think adding more scenarios to the E2E is a bad idea due to additional run time required. Instead the thread name checks can be conditionalised - e.g.

And on iOS 13 and later, the event "threads.0.name" equals "потік"