Delegate vote balance mismatch when using HTLC locks (v3)

[sebastijankuzner]

Current Behavior

HTLC lock tests sometimes fails with the message below.

FAIL __tests__/functional/transaction-forging/htlc-lock.test.ts (248.63 s)
  Transaction Forging - HTLC Lock
    ✓ should broadcast, accept and forge it [Signed with 1 Passphase] (33625 ms)
    ✓ should broadcast, accept and forge it [Signed with 2 Passphrases] (48097 ms)
    ✓ should broadcast, accept and forge it [3-of-3 multisig] (63146 ms)
    ✕ should update delegates vote balance using locked balance when voting and unvoting delegates (80175 ms)

  ● Transaction Forging - HTLC Lock › should update delegates vote balance using locked balance when voting and unvoting delegates

    expected delegate 02f7acb179ddfddb2e220aa600921574646ac59fd3f1ae6255ada40b9a7fab75fd  to have vote balance = 300009690000000, got 300009790000000

      219 | 
      220 |         const expectedBalanceAfterVoteAgain = expectedBalanceAfterLock.minus(unvote.fee).minus(voteAgain.fee);
    > 221 |         await expect(delegateToVote).toHaveVoteBalance(expectedBalanceAfterVoteAgain.toString());
          |                                      ^
      222 |     });
      223 | });
      224 | 

      at Object.<anonymous> (__tests__/functional/transaction-forging/htlc-lock.test.ts:221:38)
          at runMicrotasks (<anonymous>)

[sebastijankuzner]

Vote mismatch occurs, because voted delegate has forged a new block and collects fee. Vote balance increased for fee amount (1 ARK), because delegate has also vote for himself in genesis block.