Issue #320: Add deletion-request ping support for legacy_client_id

[psymoon]

This is following the guideline from https://mozilla.github.io/glean/book/user/pings/deletion_request.html#the-deletion-request-ping.

[psymoon]

Request for data collection review form

1) What questions will you answer with this data?

This data will be used to delete legacy telemetry data associated with the id when they opt out of telemetry.

2) Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?

This allows us to comply with user privacy regulations.

3) What alternative methods did you consider to answer these questions? Why were they not sufficient?

Existing legacy telemetry does not currently have the ability to send a deletion request ping and this was the easiest way to get that information

4) Can current instrumentation answer these questions?

N/A

5) List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories on the Mozilla wiki.

Measurement Description	Data Collection Category	Tracking Bug #
Legacy telemetry client id	Category 1	Issue 320

6) How long will this data be collected?

For the lifetime of the application, owned by the amazon-dev team.

7) What populations will you measure?

All users with telemetry enabled, on release channel.

8) If this data collection is default on, what is the opt-out mechanism for users?

There is an option in settings to stop sending usage data that will be used as the opt-out mechanism.

9) Please provide a general description of how you will analyze this data.

This will be analyzed with the normal Glean methods such as GUD and GLAM.

10) Where do you intend to share the results of your analysis?

Internally with Mozilla, through normal Glean reporting methods.

[psymoon]

Request for data collection review form

All questions are mandatory. You must receive review from a data steward peer on your responses to these questions before shipping new data collection.

1) What questions will you answer with this data?

• Verify and validate glean baseline ping side-by-side with existing telemetry

2) Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements? Some example responses:

• Ensure the baseline ping is being sent on the correct expected schedule with the expected contents, and to validate side-by-side with existing telemetry.

3) What alternative methods did you consider to answer these questions? Why were they not sufficient?

N/A

4) Can current instrumentation answer these questions?

N/A

5) List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories on the Mozilla wiki.

This only adds the Glean baseline ping (link)

6) How long will this data be collected? Choose one of the following:

For the lifetime of the application, owned by the amazon-dev team.

7) What populations will you measure?

• All Firefox for Echo Show users with who have opted-in to telemetry.

8) If this data collection is default on, what is the opt-out mechanism for users?

• Opt-out through settings.

9) Please provide a general description of how you will analyze this data.

• Glean

10) Where do you intend to share the results of your analysis?

• Glean and potentially other mobile teams

11) Is there a third-party tool (i.e. not Telemetry) that you are proposing to use for this data collection? If so:

• No