Generalise / consolidate voting logic

[maurolacy]

Currently we have a bunch of similar but slightly different implementation of the voting logic.

Moreover: we have a voting-contract package that exists to supposedly avoid that.

Voting contracts:

• In tgrade-contracts
  • tgrade-ap-voting (already uses voting-contract)
  • tgrade-oc-proposals (already uses voting-contract)
  • tgrade-trusted-circle (already uses voting-contract)
  • tgrade-dispute-multisig
• In poe-contracts
  • tgrade-community-pool (already uses voting-contract)
  • tgrade-validator-voting (already uses voting-contract)
• In cw-plus
  • cw3-fixed-multisig
  • cw3-flex-multisig

It'll be good to move / rename the tg-voting-contract package to cw-plus (or to its own repository), and change all multisigs (the ones in cw-plus, poe-contracts, and tgrade-contracts) to use it.

[ueco-jb]

cc: @webmaster128 @uint

[uint]

Makes sense. I feel like it'd more be that we'd make the cw3 spec/package properly reusable/extensible, and use it everywhere. As long as it doesn't break the spec.

Should this ticket be in cw-plus?