[BUG] Contract Action trace not finalised correctly if system contract fails early

It was observed that failing early in System Contract produces contract action with state "UNKNIOWN" instead of "REVERT". Example transactions that could reproduce the issues: updateFungibleTokenCustomFees, updateFungibleTokenCustomFees and Airdrops

Observed behaviour:
- Try to send transaction via relay for updateFungibleTokenCustomFees with 11 custom fees (invalid value for current config)
- Expect the call to revert with status CUSTOM_FEES_LIST_TOO_LONG
- Actual response status UNKNOWN

Investigate the behaviour and propose a solution.

Start by reproducing the relay transactions for updateFungibleTokenCustomFees with 11 custom fees and the listed Airdrops case, then trace how an early System Contract failure is finalized. Done means the invalid transaction reports REVERT with status CUSTOM_FEES_LIST_TOO_LONG instead of UNKNOWN.

Written by the indexing model from the issue text.