Wire index/add handler with IPNI publisher-lambda

[Gozala]

Context

System uses publisher-lambda that receives block multihashes on "Multihashes SQS topic" from which it creates and publishes IPNI advertisements. This makes blocks served by hoverboard - w3up bitswap peer discoverable on the network.

What

Put all the multihashes in the dag index (passed into #1401) into multihashes queue that publisher lambda reads from.

Why

Without this network will not be able to discover that our bitswap peer serves blocks stored via blob/add and published index/add capabalities.

Delivered

1. When done one should be able to query IPNI and discover that blocks added through blob/add + index/add are provided by w3up bitswap peer.
2. Once Wire index/add handler to write derived hoverboard block level index #1405 is also done one should be able to access content added through blob/add + index/add via kubo node without manually connecting it to w3up bitswap peer.

[alanshaw]

resolved in storacha/w3infra#363