[Reverted TX related] Transactions will execute successfully when `actual_fee > max_fee` and will charge `max_fee`

[xqft]

Right now a transaction will not fail its execution when its fee exceeds the max_fee set by the user, and will charge this max_fee if the tx is of version > 0.

We'll need to charge max_fee before failing, and apply revert logic instead of making the function return an error.

Thanks to Fabijan from ShardLabs for reporting this!

This problem will be solved within different PRs:

• Fail with an Err transactions whose calculated fee exceed max_fee #892
• Fix transactions bypassing the max_fee by introducing new revert logic #901
• Implement revert logic using the TransactionalState for every transaction #1003

[juanbono]

This was already fixed