imp(evm): restrict VFBC deployment on top of Module Account or EOA

[VictorTrustyDev]

Current behavior is deploy VFBC no matter account is existing or not, no matter the type of the account is. The only restriction is the existing account must Not be a contract account.
Even tho the chance of override an existing Module Account or EOA is almost equals to brute forcing private key of a wallet.
This PR can be ignored without any consequence.

Brief of code change:

• Restrict deploy VFBC if existing account is a Module Account.
• Restrict deploy VFBC if existing account has sequence number > 0 (sign of EOA, as user used private key to sent at least one transaction).

Plus the existing one (restrict deploy VFBC if existing account is a VFBC contract), we have 3.

Added test-cases:

• Proof of VFBC still able to be deployed if there is an existing account at the predicted address.
• Test cases for the new restriction as defined above.

In case VFBC was stopped deploying due to the restriction defined above. We just need to shift sequence number of the deployment module account by one and everything will be fine.