Add a Startup Option to Specify the Client ID

[Sdaswani]

Why/User Benefit/User Problem

Automated and performance testing may skew our telemetry numbers, confusing us. We don't like to be confused!

What / Requirements

Add a Startup Option to Specify the Client ID . The Client ID would be used as the id for our telemetry calls.

Acceptance Criteria (how do I know when I’m done?)

I can start up Focus with a specified client id and that is what is reported in redash.

cc @mmccorks

┆Issue is synchronized with this Jira Task

[nojunpark]

Reminder that upon completion nimbledroid / google firebase upload should be checked.

[mcomella]

This needs to change in components first: see mozilla-mobile/android-components#695

[pocmo]

FYI: For UI tests on Firebase we only upload debug builds that do not send any telemetry. To Nimbledroid we upload Nightly and Release builds though.

[pocmo]

Regarding mozilla-mobile/android-components#695:

If we add a startup option here then could this option just disable telemetry? Or do we want to actually upload the pings?

[Sdaswani]

@pocmo my thought is we should still upload telemetry so we can run tests on the client as a 'black box', e.g., if the telemetry library breaks and becomes a substantial performance bottleneck, if we shut off telemetry during startup for performance builds we would never discover that issue.

[mcomella]

I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1514336 against glean.

[liuche]

We have so few QA release tests (manual) compared to our userbase, and this requires Glean work, so we're going to close this for now because it's not important. Can re-open if we start doing more automated, release tests.