Bug 1271380 - Report search counts in core ping

[thebnich]

The first commit creates/send the core ping only if we have an active network connection. The second commit adds search recording to our SearchViewController and reports this data with the core ping.

When creating the core ping, we immediately reset the search data that we're reporting. That means if we create the ping but the ping isn't successful, we'll drop the data. That's why the network connectivity check was added to the PR: it increases the likelihood that the ping will succeed.

Unless we want to take the time to implement a telemetry fault-handling layer that stores and resends unique pings, I think this is the best we can do. The other option would be to reset the count only after receiving an HTTP 200, where we'd instead be sending potentially duplicate pings instead of dropping them. I agree with mcomella's comment that missing data is better than bad data.

[mcomella]

I'd explain why you don't try to send when you don't have connectivity – i.e. because it resets your measurements & increments seq, e.g. like your comment on this PR.

[st3fan]

I think this is a great start. We can do buffering of pings later.