sdk/state: change open/confirm/payment validations to check against ChannelState() when possible

[acharb]

right now validations for open/confirm/payment are checking against the state of the latest agreements. Now that we have an overall ChannelState() enum, we should instead (or possibly also) check against that value

[leighmcculloch]

Could you link to some validations that would change and be replaced with the new state function?

[acharb]

I think these might be it:

open validation: https://github.com/stellar/experimental-payment-channels/blob/6521706e5e22064d7d0e98ba7a4f2c6857e44cea/sdk/state/open.go#L226

propose payment: https://github.com/stellar/experimental-payment-channels/blob/6521706e5e22064d7d0e98ba7a4f2c6857e44cea/sdk/state/payment.go#L98

confirm payment: https://github.com/stellar/experimental-payment-channels/blob/6521706e5e22064d7d0e98ba7a4f2c6857e44cea/sdk/state/payment.go#L160

propose close: https://github.com/stellar/experimental-payment-channels/blob/6521706e5e22064d7d0e98ba7a4f2c6857e44cea/sdk/state/close.go#L95

confirm close: https://github.com/stellar/experimental-payment-channels/blob/6521706e5e22064d7d0e98ba7a4f2c6857e44cea/sdk/state/close.go#L124

[acharb]

we might want to add the same validation for checking if already closed / closing too 🤔

[leighmcculloch]

I think the first four spots you linked to make sense and look like good candidates for that. The last spot less so because the guard is checking an authorized close agreement exists before copying it and modifying it for early closure.

[acharb]

adding next steps for when I or someone jumps back on this.

We'll need to add more granular states for the open steps. @leighmcculloch 's suggestion:
#270 (comment) .

Probably 2 PRs to complete:

1. add the missing states, and assert them in the tests
2. swap out the validations to use these new channel states