Share workarounds with cargo-about

[Jake-Shadle]

I added workarounds to cargo-about since there are a lot of crates, even widely used ones, that make machine reading of the license impossible or actually don't package the license text at all, even though it is a requirement of many licenses to do so. Having workarounds that users can easily apply rather than providing clarifications would be a nice quality of life improvement, in addition to #121. Eg. #389.

[Jake-Shadle]

Actually when thinking about this recently I think the best path forward is to go back to an earlier idea I had which is to store these shared clarifications in a public github repo, similar to how the rustsec advisory db works, that allows community contributions rather than code.

While ideally crates would be able to fixed at the source, that is just unfortunately not going to happen for all crates, for a variety of reasons, as much as I would like it to. Also, the ideal fallback would be clearlydefined.io, but unfortunately that service, is incredibly slow, and the way it works means that someone needs to request <crate>@<version> at some point for the slow harvesting to even begin, which is immensely wasteful as 99% of versions are going to have the same license information as the previous version(s) of that crate.

While clearlydefined.io can still be used as a fallback, an active repo with community contributions that can be quickly updated feels like a better long term approach, even if it will essentially cover the same ground as clearlydefined.io. And also, license stuff is immensely annoying, so there is that to consider...