Bug 1633525 - Remove frecency-update pings

[fbertsch]

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)
• Scan the PR and verify that no changes (particularly to .circleci/config.yml) will cause environment variables (particularly credentials) to be exposed in test logs
• If the PR comes from a fork, trigger the integration CI test by pushing this revision as discussed in the README and review the report posted in the comments.

For glean changes:

• Update include/glean/CHANGELOG.md

[fbertsch]

Looks like the new integration tests are failing. cc @acmiyaguchi

[acmiyaguchi]

This looks like its caused by the push to integration script. The build step contains the tests for detecting diffs in the BigQuery schemas, but the CircleCI configuration filters out this step. This should resolve itself in master and doesn't block this PR.

[mreid-moz]

In Bug 1633928, there's some discussion of flagging data we wish to delete using UnwantedDataExceptions - is that going to be done here before merging this PR?

[whd]

In Bug 1633928, there's some discussion of flagging data we wish to delete using UnwantedDataExceptions - is that going to be done here before merging this PR?

Yes, we discussed this in the May 4th technical check-in and agreed that since we will likely always want to create UnwantedDataExceptions anyway (e.g. https://bugzilla.mozilla.org/show_bug.cgi?id=1635592 came eventually after the deletion in https://bugzilla.mozilla.org/show_bug.cgi?id=1626490), we can significantly simplify deploy semantics by always requiring that datasets pending deletion have all their data marked as UnwantedDataException in gcp-ingestion before the MPS PR is merged.

I'd therefore expect that before this PR is merged we'd deploy a change like mozilla/gcp-ingestion#1278.

[mreid-moz]

Please don't merge this until we've solidified the process around deleting data in Bug 1633928.

[relud]

closing this won't-fix with intent to revisit after @mreid-moz's bug is worked out.