Fix "Unable to initialize bitlist for requested keys" error when trying to accept many items

[carver]

Got this in my logs, and it seems like it shouldn't ever happen:

2024-09-25T00:47:52.235808Z ERROR trin_history::events: Error processing portal history request, responding with empty TALKRESP error=Error while building accept message: Unable to initialize bitlist for requested keys. request.discv5.id=aaa81102dc43bd18

Error is triggered here:

trin/portalnet/src/overlay/service.rs

Lines 1057 to 1059 in b28beff

	BitList::with_capacity(request.content_keys.len()).map_err(|_| {
	OverlayRequestError::AcceptError(
	"Unable to initialize bitlist for requested keys.".to_owned(),

The size of the Bitlist is defined by the Accept message here:

trin/ethportal-api/src/types/portal_wire.rs

Line 567 in b28beff

pub content_keys: BitList<typenum::U8>,

So it seems that our accept message only stores up to 8 items. The specs suggest that it should accept up to 64.

I'll open a PR to increase this to 64.

[carver]

Tangentially, I noticed a minor Bitlist bug: sigp/ethereum_ssz#33

[morph-dev]

It feels like we should add a hive tests for this as well:

• sending 64 keys should work (and they should be available after they are accepted)
• sending 65 should fail

[KolbyML]

It feels like we should add a hive tests for this as well:

• sending 64 keys should work (and they should be available after they are accepted)

• sending 65 should fail

I mentioned I would write one in Carvor's fix PR for this issue, for continuity sake.