Summary

In order for clients to be able to discover booster-http addresses via indexers like cid.contact, when it is configured, we need to add it to the extended provider announcements on startup.

We already have support for booster-bitswap announcements, so we just need to update the logic to include booster-http and handle any combination of these being enabled.

Criteria

• SP's should be able to only have booster-http enabled and its metadata announced
• SP's should be able to only have booster-bitswap enabled and its metadata announced
• SP's should be able to have both booster-http and booster-bitswap enabled and announced
• Extended provider records should be empty if neither service is configured

Dependencies

• Support for this has already been enabled for the indexers via Add IPFS Gateway HTTP transport metadata as a well-known multicodec ipni/go-libipni#22