Add party config updates to the two party POL

[bekauz]

Both parties participating in the covenant should be able to update their part of the configuration. This may include the authorised claim address, connection / channel ids, etc.

[uditvira]

We need to confirm who can update what configurations. There are two types of configurations:

1. Can be updated by a single party without the approval of the counterparty
2. Needs approval of both parties

First, we need to delineate which configuration is of type 1 and which is of type 2.

Second, we need to decide how the type 2 configurations are updated. Within this, there are two possible directions we can take: a) We offload this feature to DAODAO where a 2 member DAO can update the contract where the voting policy for changes requires both parties to approve b) We develop a minimal 2-of-2 approval system within the covenant contracts

My personal preference, to keep our work scoped and reduce redundancy is to take direction a

[uditvira]

@bekauz can you take a first stab at this:

we need to delineate which configuration is of type 1 and which is of type 2

I'll be happy to review

[bekauz]

Sure. Params in question:

• lockup period
• party configurations (controller addr, host addr, expected contribution amount and denom, ibc denom, channel and connection ids, ibc transfer timeout)
• pool address
• ragequit configuration
• deposit deadline
• share of the position
• expected pool ratio
• acceptable pool ratio delta
• pool pair type
• denom splits

[uditvira]

We should prioritize adding methods for a single party to update their own configs where the second party's approval is not required.