Think about the design of the voting contract example

[eloylp]

Context

During #12 , we were asking ourselves questions regarding its design. Initially, a single voting contract can hold multiple proposals. This was done in this way instinctively in order to try to reduce fee costs when deploying new contracts to the network. However, this needs more investigation .

Goals

• Evaluate if the current design (multi proposal contract) would make sense for this contract library or should we change it for a single proposal per contract.
• Do needed changes or additions.

[eloylp]

I was wondering if this could be a good exercise:

1. To create the simple version (proposal per contract) .
2. Adapt the current version (multi proposal per contract) to reuse the logic of the simple one 1.
3. Try to make this optional in the wizard UI. See how that would work.

[eloylp]

The simple voting contract was created here https://github.com/eigerco/nebula/pull/39 due to #25