Add support for classifying invalid compatibility reports to the http service

[ksy36]

Fixes #3839

[ksy36]

r? @suhaibmujahid @marco-c

[suhaibmujahid]

LGTM! Thank you!

[marco-c]

LGTM! If we get too many, we might want to have a separate queue with a lower priority so that we don't impact the other API endpoints too much. Let's see how it looks after deployment.

[ksy36]

LGTM! If we get too many, we might want to have a separate queue with a lower priority so that we don't impact the other API endpoints too much. Let's see how it looks after deployment.

Sounds good. We've shipped the reporter in Nightly on desktop about a week ago and got about 150 reports so far (only 80 have description and would have needed classification). But I think most of these reports are from QA testing the feature :)

[ksy36]

Thanks!

[marco-c]

@ksy36 when would you like to see this deployed?

[ksy36]

@ksy36 when would you like to see this deployed?

Would it be possible to deploy this some time next week? (I was thinking to start working on an ETL script that will use this endpoint then)

[marco-c]

Sure! I will deploy a new version now, so we can root out any potential bugs now and retrigger a new release if necessary.

[ksy36]

Perfect, thank you!

[marco-c]

I released a new version and triggered a new pipeline run: https://community-tc.services.mozilla.com/tasks/groups/NSVaUXIURx6zKSUcsItQZw. In a few hours, the new API endpoint should be available.