eFuse API misleading with regards to eFuse field widths

[kyrias]

The new eFuse API implemented in #847 is a bit misleading to use, and in fact many of the generated EfuseField definitions that it included lead to a panic if you try to read them using Chip::read_efuse.

EfuseField appears to support defining fields that are wider than a single 32-bit word, and many of the generated definitions do exactly that, but Chip::read_efuse only supports reading fields of at most 32 bits. Passing in a field wider than that leads to a "attempt to shift left with overflow" panic.

[dimpolo]

Actually it's even worse:
for example in target/efuse/esp32s3.rs:

pub const ADC1_INIT_CODE_ATTEN1: EfuseField = EfuseField::new(2, 4, 157, 6);

This field is only 6 bits wide but it's situated in block 4 AND block 5.
espflash only reads block 4 and quietly reports the wrong value

[kyrias]

Hmm, yeah, that's not great, though I'd argue it's kind of a different though related bug. This should be pretty easy to fix without changing the API though.

[kyrias]

@dimpolo Could you try out this PR? #968