bug 1955428 - Add client_info.attribution and client_info.distribution

[chutten]

Checklist for reviewer:

• Commits should reference a bug or github issue, if relevant (if a bug is referenced, the pull request should include the bug number in the title)
• If adding a new field, the field should have a description (see Bug 1652842 - Add a blocklist field so the environment schema works with pre- and post-bug-1647225 data #576 for an example)
• [in progress] If coming from a fork, run integration tests: ./.github/push-to-trigger-integration <username>:<branchname>

For glean changes:

• Update templates/include/glean/CHANGELOG.md

For modifications to schemas in restricted namespaces (see CODEOWNERS):

• [n/a] Follow the change control procedure

[chutten]

Here's the trigger-interaction push: https://app.circleci.com/pipelines/github/mozilla-services/mozilla-pipeline-schemas/3894

[chutten]

(whoops, didn't see auto-assign bot there.)

[chutten]

@BenWu Actually, come to think on it, will these need to have space for client_info.{attribution|distribution}.ext for the column replacement in mozilla/bigquery-etl#7252 to work?

[BenWu]

Yes I think the column needs to exist for REPLACE to work but I also think replacements don't work for nested columns so it wouldn't work anyway. You might need to recreate the client info struct like this normalization UDF does https://github.com/mozilla/bigquery-etl/blob/df42f75dd3a48a8eaaa98abc72d7665369c2dbb8/sql/mozfun/norm/glean_baseline_client_info/udf.sql#L12-L15

[chutten]

With column replacement being taken as a follow-up in https://mozilla-hub.atlassian.net/browse/DENG-8208, this can merge as-is.