Token Manager: creating new votes through a token manager can cause skewed votes

[sohkai]

If a Token Manager holds the governance token for a voting app, either because someone transferred tokens to it or it issued tokens to itself, and a vote is created by forwarding through the Token Manager, the Token Manager will automatically vote "yea" based on its current holdings.

Some potential ways to solve this:

• Don't vote automatically when creating votes through a forward: the same UX as now would be possible, but could be difficult to implement generically, as aragon.js would need to provide a hook to get more information about the voting app and how to make direct transactions again it; also makes it impossible for another app to vote unless directly implemented, although some could argue that's a feature
• Check if the msg.sender in the Voting app's forward() is a contract: can't be 100% sure, and has same second drawback as above

[sohkai]

Another way to fix this is to remove the forwarding functionality from the Token Manager itself, and use a "Token balance" trigger instead as the forwarder.