Discussion: should codecs explain the type of data they support while decoding

## Context

It looks like [infectious](https://github.com/vivint/infectious) supports decoding data where some shards have been corrupted. On the other hand, klauspost/reedsolomon leopard does not support decoding shards that have been corrupted [ref1](https://github.com/klauspost/reedsolomon/blob/fd3e6910a7e457563469172968f456ad9b7696b6/README.md?plain=1#L215),
[ref2](https://github.com/klauspost/reedsolomon/blob/fd3e6910a7e457563469172968f456ad9b7696b6/README.md?plain=1#L173-L174).

Questions:
1. Should the codecs document this behavior?
2. How can Celestia use Leopard if shares are corrupted? Is there a mechanism to ignore corrupted shares?

Begin by comparing the README sections linked for infectious and klauspost/reedsolomon Leopard, then trace how rsmt2d's codecs handle corrupted shares during decoding. Resolve whether this behavior should be documented and how Celestia can use Leopard with corrupted shares; done when both questions have an agreed, documented answer.

Written by the indexing model from the issue text.