bug: deriving serde::{Serialize, Deserialize} on padding: [u8; >32] breaks

[OliverNChalk]

When generating the interface for a contract that has a padding fields >32 bytes serde will complain with:

the trait bound `[u8; 46]: Deserialize<'_>` is not satisfied the following other types implement trait `Deserialize<'de>`:
  [T; 0]
  [T; 1]
  [T; 2]
  [T; 3]
  [T; 4]
  [T; 5]
  [T; 6]
  [T; 7]

Some options are:

• Skip serde for structs with large arrays.
• Use serde_with (https://docs.rs/serde_with/3.6.1/serde_with/guide/serde_as_transformations/index.html#big-array-support)
• Use serde-big-array

[billythedummy]

Haven't had time to work on this in a while, apologies.

In retrospect, the serde feature was kinda half-baked because from our experience, it's being used in a json context most of the time, which would require additional custom de/serialization logic anyway like de/serializing pubkeys as base58-encoded strings instead of byte arrays, serializing u64s as strings instead of javascript numbers to avoid issues with Number.MAX_SAFE_INTEGER.

I would recommend just turning off the serde feature on the generated crate and handling serde on your own. We might even remove the serde feature in the future.