Panic on Key Overflow in Dictionary Builders

[tustvold]

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

I suspect this will be a controversial issue, but there a couple of reasons for proposing this

• Rust collections and accompanying traits like FromIterator and Extend assume infallibility
• We currently panic on offset overflow for StringArray, ByteArray, ListArray, etc...
• We already panic on offset overflow in FromIterator for DictionaryArray
• The error is just going to be surfaced to the user anyway, a panic is perfectly acceptable for this imo

Describe the solution you'd like

Panic on key overflow instead of returning an error

Describe alternatives you've considered

We could implement Extend and panic on key overflow there, much like we do for FromIterator, but I feel we should be consistent about this.

We could also implement our own TryExtend trait or something similar.

Additional context

#2725 tracks a more holistic rework of how we handle errors

[alamb]

My personal opinion is that the client code should be able to avoid panic's if the user desires, but that doesn't mean the API needs to be fallible.

For example, as long as it is possible to pre-compute / estimate when a panic would occur (either explained via docs or some sort of calculation with https://docs.rs/arrow/31.0.0/arrow/array/struct.ArrayData.html#method.get_slice_memory_size or something) then 👍

[tustvold]

label_issue.py automatically added labels {'arrow'} from #3563

[tustvold]

label_issue.py automatically added labels {'parquet'} from #3553