Smart Contract - Refactoring code and dependancies upgrade

[bal7hazar]

Description

With the new Cairo 0.10.0 we have to update our smart contract code to keep up-to-date.

Because we will have to go through all the code, it could be a good opportunity to refactor additionnal code according to latest guidelines.

Upgrade the following deps:

• openzeppellin v0.4.0
• protostar v0.5.0

Few ideas:

• Move protostar version from secrets to job env (to avoid to have failing CIs in PRs)
• Add unit_256 checks for all Uint256 inputs (see function in OZ ERC-1155)
• Re-entrancy security improvment (guard feature when interfaces are used in contracts)
• Check-Effect-Interaction compliance when transfer ERC-20 tokens
• Constructor to Initializer for libraries
• _iter suffix for loops
• Move owner assertions from library to contracts

What code could be improved?

All cairo files and python files (Cairo 0.10.0 also change python version from 3.7 to 3.9)

Acceptance Criteria

• Tests on refactored code succeed
• Deployements on refactored code succeed

Additional context

OZ released a new version of their contracts according to the new cairo version.
A new version of protostar has been released supporting cairo version.

We need a new release of Cairopen before the migration.