Initialize NextSequenceSend in ProvideCounterparty handler

[DimitrisJim]

Raised by @colin-axner in https://github.com/cosmos/ibc-go/pull/7174/files#r1752160538:

Lets initialize the packet sequence when setting the counterparty? This would allow us to remove the if's in send packet. I feel like calling ProvideCounterparty should be viewed as finalizing the communication details

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged/assigned
• Estimate provided

[damiannolan]

We currently set the NextSequenceSend nonce in SendPacket here, where we have access to a port identifier as dictated by the application.

The ics24 path used here is the existing v1 path, which includes the port identifier. In v2/eureka, I would expect the ics24 path to not include the port id.

Currently, we do not have any port id within scope in the ProvideCounterparty rpc handler, and I would not expect there to be one.