Reflect payment expiry changes

[hydra-yse]

This PR:

• Changes the occurrences of GetInfoResponse to use its new inner field of type WalletInfo
• Adds the liquidExpirationBlockheight and bitcoinExpirationBlockheight fields to the lightning and bitcoin payment details

[dangeross]

Is the scope of the PR only to reflect the SDK changes or do you plan to show the payment expiry time in the payment model also?

[hydra-yse]

Is the scope of the PR only to reflect the SDK changes or do you plan to show the payment expiry time in the payment model also?

Don't know much about UI changes, but seems like a minor addition. I can add it if necessary. What do you think @roeierez?

[roeierez]

Is the scope of the PR only to reflect the SDK changes or do you plan to show the payment expiry time in the payment model also?

Don't know much about UI changes, but seems like a minor addition. I can add it if necessary. What do you think @roeierez?

I think we should make it minimal only to have a build so we can test. Any additional features to misty can be done in a following PR outside the milestone. The main goal is to have today a build based on the sdk milestone so we can test and release RC

[erdemyerebasmaz]

Made suggestions to use WalletInfo directly instead of GetInfoResponse on methods of WebhookCubit.

ℹ️: These changes may affect other parts of the code.

[erdemyerebasmaz]

LGTM