Catch error in proof of work to get contracts parsing error

[samuelmanzanera]

Description

This PR resolves an issue occurred when you are passing invalid smart contract code to the network.
The Proof of work was trying to parse the contract to get the origin family, but without catching the error.

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Create a transaction with invalid keyword in the contract, it should return an invalid transaction with the error returned as "unexpected-token - xxxx - LX"

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[apoorv-2204]

we might have some test cases?

[Neylix]

Hello,
It's not part of your change, but you can fix a bug in this PR.
In the Worker module, the function handle_new_transaction broadcast the message StartMining but it do not do the validation node election before. This cause an invalid node election when other node start mining.
This function should use Archethic.send_new_transaction(tx)