Mark issues/PRs for known-tainted builds

[rettichschnidi]

Introduction

Now that tainted builds are getting exposed (#79980), and such builds can be recognized by their logs (e.g. #80180), I propose to label issues and PRs with such logs attached as tainted.

Problem description

Debugging problems when blobs are involved is hard(er). Making their presence more visible respects peoples time.

Proposed change

1. Create label tainted on GitHub
2. Add automation to grep issues for the string *** Booting Zephyr OS build (tainted) and adding the label tainted to the issue.

Detailed RFC

TBD

Proposed change (Detailed)

TBD

Dependencies

• CI infrastructure to read and act on text posted in issues

Concerns and Unresolved Questions

• False positives: Discussions happening in an (actually blob free) issue could contain the *** Booting Zephyr OS build (tainted) string due to reasons unrelated to the build the issue was originally reported for.
  • Chances are probably low, and manually dismissing the label might be a good enough countermeasure
• Not all issues contain the full logs
  • True, but doing a best effort labeling still makes the situation better for all
  • One can still manually add the label

Alternatives

• Manually adding the label