State: mozilla-l10n/android-l10n@e521a2aab2cc7d45f47523f7c620cb5c4228ff89

Co-authored-by: vladikoff <vlad.filippov@gmail.com>

Also in this commit:

Explicitely test that double-stopping doesn't change the value

The way it is currently implemented this works "by accident".
It's correct in that the timer gets deleted anyway on the first stop,
it might have not been thought of when writing it that way though.
The timespan metric keeps the `timerId` around, but the underlying
timing manager deletes this ID.

Don't overwrite existing value when raw API is used after a timer

This essentially works the same way "by accident" as the double-stop in
the previous commit.

Adjust documentation of raw API

State: mozilla-l10n/android-l10n@64a8eca673475543a4c976ce952c7421882965fb

This includes two metrics defined in a metrics.yaml inside of lib-crash that instruments a labelled count representing each type of crash: uncaught exceptions and native code crashes.

Issue #3432: feature-tab-collections: Restore Session objects and lists of Sessions instead of a Snapshot.

For toggleDesktopMode()