Add counterpart for AntiFeature / FLOSS-Status
We currently can not guarantee fully-floss build. Even if we verified everything and upstream is known to be "good", once we set AUM, we wont get notified if upstream adds a jar file. @mvdan had once experimented with disabling binary builds, which currently will break to many builds.
I'd like to have an automated check for binaries in every build that also updates the metadta accordingly. E.g. by including a counterpart for antifeatures, like "FlossStatus:NoBin" or "FlossStatus:Tainted"
However, those notes would only target the latest build, so maybe we need to include such information in the Build section?