Advertise booster-http identity in IPNI advertisements

### Checklist

- [X] This is **not** a question or a support request. If you have any boost related questions, please ask in the [discussion forum](https://github.com/filecoin-project/boost/discussions).
- [X] This is **not** a new feature request. If it is, please file a [feature request](https://github.com/filecoin-project/boost/issues/new?assignees=&labels=need%2Ftriage%2Ckind%2Ffeature&template=feature_request.yml) instead.
- [X] I **have** searched on the [issue tracker](https://github.com/filecoin-project/boost/issues) and the [discussion forum](https://github.com/filecoin-project/boost/discussions), and there is no existing related issue or discussion.
- [X] I am running the [`Latest release`](https://github.com/filecoin-project/boost/releases), or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.

### Boost component

- [X] boost daemon - storage providers
- [ ] boost client
- [ ] boost UI
- [ ] boost data-transfer
- [X] boost index-provider
- [ ] Other

### Improvement Suggestion

Currently, extended providers used by boost does not translate to the keypair identity within booster-http. As that identity becomes meaningful, as it will as https://github.com/filecoin-project/boost/issues/1610 is addressed, we will need the same delegation to occur as is present for booster-bitswap.

Read issue 1610 first to understand why the booster-http identity matters, then compare the existing delegation in booster-bitswap with the booster-http path. Done means extended providers advertise the keypair identity through booster-http in the same way as booster-bitswap.

Written by the indexing model from the issue text.