Add retry function

[nmlinaric]

Description

Function that emits Retry event which triggers the retry failed deposit process on the MPC side.

Related Issue Or Context

Closes: #542

How Has This Been Tested? Testing details.

Unit tests

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation

Checklist:

• I have commented my code, particularly in hard-to-understand areas.
• I have ensured that all acceptance criteria (or expected behavior) from issue are met
• I have updated the documentation locally and in chainbridge-docs.
• I have added tests to cover my changes.
• I have ensured that all the checks are passing and green, I've signed the CLA bot

[P1sar]

Btw I have a question, for example we are going to have 10 networks. User submits this hash on the source chain, relayers would need to search all 10 networks to found where this execution failed. So maybe we should also add dst network ID or something like that? @mpetrun5 @nmlinaric

I have new question

[mpetrun5]

Btw I have a question, for example we are going to have 10 networks. User submits this hash on the source chain, relayers would need to search all 10 networks to found where this execution failed. So maybe we should also add dst network ID or something like that?

We will find all data from initial Deposit event related to that transaction hash (which is of a deposit event).

[P1sar]

Oh yes for sure