[EPIC] Tag all spans during app start with start type info

[narsaynorath]

For the mobile starfish app start module we want to allow users to be able to filter their spans by warm/cold start. We've decided to propagate a start type property in span data to facilitate this filter.

I propose adding a key called app_start_type to the span data field (docs on the data field) which can either have a value of cold or warm.

Tasks

Preview Give feedback

1. Android: Tag all spans with app_start_type sentry-java#3989
   Platform: Android Platform: Java +2
2. Tag all spans with app_start_type sentry-cocoa#4715
   Platform: Cocoa +1
3. Tag all spans during app start with start type info sentry-react-native#4460
   Platform: React-Native Span Streaming +2
4. Tag all spans during app start with start type info sentry-dart#2525
   Platform: Dart +1
5. feat(app-start): Tag spans with start type relay#3027
   +0
   

The linked Relay PR will start filling in app_start_type by checking the measurements on a transaction to see if there is app_start_warm or app_start_cold timing. If the value is provided in the data field, then that will take precedence. This is so we can take advantage of the filtering before waiting for new SDK adoption, but will support extraction when moving towards span streaming.

It was suggested to use app context but it seems like Android may be missing the start type for certain transactions, e.g. see here. This seems like the most consistent method across Android and iOS at the moment.

[kahest]

@markushi do we still need this? Or on the other hand, do we only need this once Insights/product use app start info from spans vs. transactions?

[markushi]

(@narsaynorath correct me if I'm wrong)

Yes, we'd still need this, as it would allow us to filter the span table based on the top App Start Type selection: