Replace From<Vec<_>> impls with TryFroms for FixedSizeBinaryArray

[quantumish]

Which issue does this PR close?

• Closes FixedSizeBinaryArray implements From<Vec<&[u8]>> etc despite conversion being fallible #10018.

Rationale for this change

There isn't a clear way to fix the From<Vec<_>> implementations for FixedSizeBinaryArray that wouldn't be confusing, so making them TryFrom is a better fit since they are in genuine use across e.g. tests within the Arrow library as well as a terser way of calling FixedSizeBinaryArray::try_from_iter or FixedSizeBinaryArray::try_from_sparse_iter.

What changes are included in this PR?

• Converts From<Vec<&[u8]>>, From<Vec<&[u8; N]>>, and From<Vec<Option<&[u8]>>> implementations for FixedSizeBinaryArray to TryFrom implementations.
• Adds a TryFrom<Vec<Option<&[u8; N]>>> implementation for the missing combination of types.
• Updates various test cases within the arrow/parquet libraries to use try_from().unwrap() instead of from().

Are these changes tested?

This is sort of a transparent change in that only the API for expressing failure cases has changed rather than the actual failure cases. All existing tests surrounding conversion failures have been updated to check whether a conversion has correctly failed.

Are there any user-facing changes?

Yes, this is a breaking API change since user-facing trait implementations have been replaced with different trait implementations.

[alamb]

Thank you @quantumish -- this makes sense to me and I think is reasonable to avoid panic's

If other maintainers feel otherwise, we could potentially leave the old from impls

[etseidl]

This does seem more correct, but elsewhere we've kept both fallible and infallible APIs, but there we could explain the difference in the docs. Here, as @quantumish notes, From mandates a perfect infallible conversion, which the current code breaks.

TLDR I don't think we need to keep the old impls.