Issues found in ecosystem

Our primary goal with Blin is to make sure that no release introduces failures to an ecosystem module. A secondary goal is to identify those modules that don't install/test clean, and notify the module owners (via ticket) so they can resolve the issue.

• We need to add a diagnostic output as part of a full blin run (maybe in overview) that shows module owner as well as name/status. This will enable ecosystem authors to easily see what they might have to work on. The results are already stored in coke/raku-blin-release-results, but could be easier to consume

• We can skip modules via a config file now, and add in a reason for the skip - if there's an alwaysFail - we should open a ticket, link to the ticket, and skip the module in upcoming blin runs - every so often, go through and remove skips for items where the ticket is resolved.