Index methods by signature when there is ambiguity

[Stefan-Ethernal]

Description

This PR is a continuation of #1854 and it generates SC bindings in a way that they index ABI methods by signature in case the function was resolved by signature, instead of by its name (e.g. ChildERC20PredicateAccessList defines two functions with the same name but different params, which caused us some troubles in the past).

Changes include

• Bugfix (non-breaking change that solves an issue)
• Hotfix (change that solves an urgent issue, and requires immediate attention)
• New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

• I have assigned this PR to myself
• I have added at least 1 reviewer
• I have added the relevant labels
• I have updated the official documentation
• I have added sufficient documentation in code

Testing

• I have tested this code with the official test suite
• I have tested this code manually

Manual tests

1. In the ChildERC20PredicateAccessList.json artifact within the core-contracts, make sure that initialize function with 5 parameters parameters is in the first place (before the one with 8 of them, that is initializing access-list configuration)
2. Generate artifacts and bindings in the Edge, by running make generate-smart-contract-bindings
3. Run TestE2E_Bridge_Transfers_AccessLists and make sure it is executed successfully (namely it does not fail after first withdrawal being made)