bitlist maxSize off by one and inconsistent progressive list default limits

Two small follow-ups from #545, noticed while wiring the limits into lodestar (ChainSafe/lodestar#10042).

- `BitListType` and `ProgressiveBitListType` compute `maxSize = Math.ceil(limitBits / 8) + 1`, which over-estimates by one byte when `limitBits` is not a multiple of 8 (limit 7 gives 2, the largest encoding is 1 byte). Exact is `Math.floor(limitBits / 8) + 1`.
- `ProgressiveByteListType` defaults its limit to `PROGRESSIVE_LIST_MAX_SIZE` while `ProgressiveListBasicType`, `ProgressiveListCompositeType` and `ProgressiveBitListType` default to `Number.MAX_SAFE_INTEGER`.

Both are harmless as `maxSize` is only used as an upper bound, noting for consistency.

Start by locating the BitListType, ProgressiveBitListType, ProgressiveByteListType, ProgressiveListBasicType, and ProgressiveListCompositeType definitions. Check the maxSize calculation and each default limit, then run the relevant existing test suite to verify the byte bound and progressive-list defaults are consistent.

Written by the indexing model from the issue text.