Move `multiaddr_to_route` to `NodeManager`

[adrianbenavides]

ref: https://github.com/build-trust/ockam/pull/4172#discussion_r1119863015

• Leave CloudRequestWrapper as is it but with a multiaddr() function just returning a parsed MultiAddr
• Have the function multiaddr_to_route be a method of NodeManagerWorker/NodeManager in order to be able to access all the created transports internally to do the necessary connections

This means that many calls in ockam_api files will look like:

let cloud_route = self.multiaddr_to_route(req_wrapper.multiaddr()?).await?;

We love helping new contributors! If you have questions or need help as you work on your first Ockam contribution, please leave a comment on this discussion. If you're looking for other issues to contribute to, checkout this discussion and labels - https://github.com/build-trust/ockam/labels/good%20first%20issue or https://github.com/build-trust/ockam/labels/help%20wanted

[0xkelvin]

@adrianbenavides please assign to me

[0xkelvin]

@adrianbenavides is it still valid for me

[adrianbenavides]

Sure! I was reviewing the work to be done here and I noticed we use the multiaddr_to_route as a static function outside of the ockam_api crate, so we should end up with two methods:

• a static multiaddr_to_route function (the one we already have), that will be used in those places where we don't have a NodeManager instance anywhere
• NodeManager::multiaddr_to_route that will be called within the ockam_api, and internally will use the static multiaddr_to_route function

Let us know if you need help or have any question along the way!