Lassie HTTP + booster-http tracking issue

[hannahhoward]

What

We want Lassie to download over HTTP from booster-http. This issue tracks what is needed for this to happen.

Components

Updated 6/12/23 to reflect current state and detailed steps to merge

• Boxo support for IPIP-402 parameters 6/12/23 -- released in boxo v0.10.0
• Bubble Boxo through to boost - DRI: Tornado (some of this work may be done Stewards, but Tornado is responsible for watching, monitoring, assisting, and making sure this gets done)
  • resolve go-merkledag issue go-merkledag duplicates and global variables ipfs/boxo#291 6/12/23 -- is this done?
  • complete go-fil-markets boxo migration chore: migrate to boxo go-fil-markets#792 Hannah to take over
  • complete Lotus Boxo migration chore: migrate to boxo lotus#10921 Hannah to take over
  • complete Boost GFM migration Chore/use go libipni (#789) boost-gfm#2
  • complete Boost integration update boxo #1492 (note: this may not ultimately be mergable till all of the above are in tagged releases)
• Announce booster-http metadata to indexers when it is configured #1407 - PR is in (feat: http index announcements #1418), but appears abandoned. @dirkmc do you want to finish this? should Tornado?
• local devnet test between Lassie and Boost, using direct peer fetching DRI: Tornado
• fil-collins test round trip with Lassie and Boost, with indexer integration DRI: Tornado with support from Boost
• external SP testing as needed prior to release DRI: Boost
• update to tagged dependency releases and merge final boost PR, cut Boost release DRI: Boost

[jacobheun]

Thanks for creating this and linking to the various dependencies @hannahhoward, super helpful ❤️

[davidd8]

@hannahhoward can we add a task around metrics cleanup for http retrievals attempts for SPs to distinguish from other HTTP providers, like web3.storage?