fix: consensus deploy contract when finalized

[kstroobants]

Fixes #708

What

• Redo the change so that the contract is deployed when the transaction is finalized. I could not find any other issue than the issue where the appeal window loop does not recover, that blocks the transaction to go to the finalized state.

Why

• To fix a bug

Testing done

• Tested the bug fix in the localhost and ran the consensus unit tests locally

Decisions made

Checks

• I have tested this code
• I have reviewed my own PR
• I have created an issue for this PR
• I have set a descriptive PR title compliant with conventional commits

Reviewing tips

Run studio and see code changes

User facing release notes

Contract is deployed when the transaction is in the finalized state after waiting for the finality window. The write methods will be accessible when the transaction is in the finalized state.

[kstroobants]

I won't merge this PR before there is a user friendly solution in the main branch to change the finality window in .env or we put the default on a low number.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[kstroobants]

Closed because it was implemented correctly.

When a transaction tx1 is sent to deploy an intelligent contract then from the accepted state you are able to submit the next transaction tx2 towards that intelligent contract.