Manage Default Lifecycle metrics

[#1]

We should have the ability to control default lifecycle metrics behavior in the Mobile SDK configuration. This would include toggling whether or not events such as app launches automatically trigger lifecycle tracking, so that they might be manually sent or disabled entirely.

[#2]

Hi - thanks for the submission. In order to better understand the business need for this request, will you please provide the use case or business need for manually managing which metrics are sent or disabling them?

Thanks,

Roger

[#3]

Business cases could include:

1. attaching additional data to default lifecycle events
2. disabling events without value justifying their cost
3. delaying the transmission of an event for proper sequencing

Our current pressing issue is #1/#2. We have a slew of information we need to transmit when a user launches the app; however, we can't include it in the launch event. This renders it nearly worthless to us since we are forced to make a trackState call for every launch. It's similar to having to make two s.t() calls on the single webpage.