Is your feature related to a problem?

When path is being constructed for the packet, translation is required from PeerId to on-chain Address type.
On several different places also the inverse is needed.

This is currently performed by an implementation of PeerAddressResolver asynchronous trait (see

Describe the feature you'd like

Ideally, this managed via a translation table in memory so the DB does not need to be queried, thus making outgoing and forwarded packet processing significantly faster.

The table should work as LRU cache, causing it to hit the DB backend only once an entry expires.

Refs #5891