This reverts commit 624eeb7d20f8256edb0d0d7f497a4e67e4d3d751.

Move broadcast creation to CMasternodeBroadcast

Masternodes should be allowed to announce ipv4 addresses only from now on

Former-commit-id: 7bd564e7406d6b0a4d65689248fd82d8d358c822

Former-commit-id: 3484b7f1fec59b0b87626529f1b834adb5f38f6c

Former-commit-id: 36d37e28ef6a33b23bc7c845868ab3bb7c4f56c2

Former-commit-id: baf86891f001bb428dc335c81b201151c9274b15

Former-commit-id: 538ea1fd3eb6ef70ce75be987134173cad0eb75c

Former-commit-id: ec56b0a1d855649c5e0d920b89ce69293b99c25d

256e02f see 40f0d1f1dc6782d640beb925b14a7eccc6fbd69a and c96284a7879b02fdc365a9bb2e28fd8199c01e91 for more info

* Implement 12.1 MN signatures
* Remove redundant parts from v11->v12 migration

- Masternodes can only vote once per hour now, instead of 100 times a day total
- UI reports back errors now

- Ping every 5 minutes
- Nodes will propagate pings every 10 minutes

- better names (MASTERNODE_INITIAL was defined twice before that)
- move to proper header

- Do not rely on local lastTimeSeen and requested fRequested anymore. Use last know (signed) ping instead and base all logic on that. Should reduce mn list difference between
 nodes.
- Rework CActiveMasternode accordingly along with states, errorMessages, rpc etc.
- Clean some related code, move parts from public to private
- drop c_str in LogPrintf that were related to this functionality (todo: drop it for LogPrintf everywhere else)

-Syncing now happens in stages. Masternodes and Sporks, then Masternode winners, then proposals. Some of these require the masternode signatures, otherwise there are race conditions within the syncing process itself.
-Resigning - When a proposal is sent to the network initially it's signed by a masternode, if that masternode goes inactive the proposal becomes invalid. Resigning allows other masternodes to update proposal keep it valid with the coming and going of masternodes.
-Resigning compatibility - non masternodes will scan and flag proposals as invalid to accept updated owners.
-Invalid votes are now actively removed from the proposals when they go inactive
- Remove budgets with negative votes of more than 10% of network
- Only allow proposals into budget that have more than 10% of network support
- Faster removal of inactive masternodes

- With nodes coming and going on the network, the network could come to different opinions about who should get paid next in line due to some nodes being flagged as failing a PoSe check. This will have to be fixed by introducing a blockchain based PoSe system, but that's out of the scope of this release. To fix the issues in the interrim, I'm removing PoSe checks for the time being.

- Masternode nLastPaid is removed and a new caching system that keeps the last 30 days of coinbase payees replaces it
- To deal with some significant attack vectors, the masternode donation feature was removed. The donation feature was added to support developement anyway, so this will be replaced by the budgeting code.
-  This code should allow the network to come to consensus about who should be paid pretty effectively