Transport layer: HTTP request info in batch mode

[TheRealAgentK]

Please describe your new feature request
Stemming from a discussion on #321, we want simplify the structure of the HTTP information in crash report promises when the provider runs in batch mode.

Describe the solution you'd like
When the provider is in batch mode, there's no point in building up crash report promises with HTTP request information because eventually this information is all discarded and not used. The HTTP request information for batches is used instead.

Without changing the overall flow too much, we should be able to not build up the aforementioned structure in the first place.

An alternative option might be to treat the promises in a similar way to how they are being dealt with in the case of offline status (resolving with null).

[TheRealAgentK]

Done via #332