upgradeAddress does not support requester authenication

[frrist]

When setting up a compute node, you can specify an HTTP multiaddress instead of a P2P multiaddress. In this case, the compute node initiates an HTTP connection to the requester to fetch the peer ID by accessing the endpoint api/v1/agent/node. Using this peer ID, the compute node then constructs a P2P address for the connection. The process of converting an HTTP address to a P2P address is managed by the upgradeAddress method. However, this method currently doesn't include the necessary authentication headers, leading to connection failures with requester nodes that demand authentication.

[frrist]

As we move away from libp2p this will become a non-issue as NATs doesn't have requirements around public keys in connection strings.

[frrist]

This issue has been mitigated by opting to deploy NATS networks (see #3089). Since we are adopting NATs this will be unneeded.