TransportTuple: must replace uint64_t hash with new `PortManager::PortRangeKeyHash`

[ibc]

Same as done in PR #1812 (see related issue #1805) must be done in TransportTuple to replace its uint64_t hash member.

Read more detail sin #1812 (comment).

CC @penguinol @999purple999 to be in sync about this.

[ibc]

@999purple999 said:

Re #1815: happy to take the TransportTuple follow-up once this lands. The same struct + hashCombine pattern should drop in cleanly; the only piece worth thinking through is whether TransportTuple wants PortRangeKeyHash as-is or its own type since the key shape differs (no min/max port range there). I'll open a PR against #1815 next week unless @penguinol gets to it first.

I think a separate struct/type is better because, indeed, it's not the same.