Fix or silence most common SENTRY issues

[Archaeopteryx]

From code-review-bot

[La0]

Most common issues are currently:

• in events, missing m-c repo on Phabricator with 1700 events & ongoing
• in bot missing clang-format has 2k+ events
• in bot, a new issue since 1.7.4 about missing warnings

A lot of warnings in the bot could also be silenced by simply lowering the log level to info

I resolved this one which seemed to be a Taskcluster issue over the past week (no new events)

[marco-c]

The first one, missing m-c repo, is only happening on testing. Testing has the following in the list of repositories:

    - checkout: robust
      try_url: ssh://hg.mozilla.org/try
      try_mode: json
      try_name: try
      name: m-c
      ssh_user: reviewbot
      url: https://hg.mozilla.org/conduit-testing/m-c/
      decision_env_revision: GECKO_HEAD_REV
      decision_env_repository: GECKO_HEAD_REPOSITORY
      decision_env_prefix: GECKO

The problem is that this repo is only available on Phabricator dev, and at the moment testing is pointing at Phabricator prod.

[La0]

I filed 2 issues for @vrigal on the bot, and removed the MC repo from testing secret, then restarted code-review events testing o, heroku. This sentry issue is now marked as resolved

[La0]

I just noticed another config problem (on this task):

2024-08-29 12:17:48.000824 [WARNING ] [warning  ] Backend rejected the payload: b'{"base_repository":["Object with url=https://hg.mozilla.org/comm-unified does not exist."]}'

I do not know if we want to track this repo or not @marco-c @Archaeopteryx

[Archaeopteryx]

comm-unified is similar to mozilla-unified would be by assumption - and development with mozilla-unified i prefered compare to a checkout of every stage of the development cycle/ESR branch (central, beta, release, esrXXX).

I am in favor of supporting it.

[marco-c]

comm-* used to work, but I think it is not working anymore, see #2042. We should fix that, and it will likely make this error disappear.