chore: transform contracts repository into forge repository and fix the ERC20 bytecode deployment issue

[leovct]

Description

Fix

• Generate a new version of the ERC20 bytecode. It was always reverting during the deployment.

Chore

• The contracts/ folder is now a foundry project which makes it easier to handle dependencies.
• ERC20.sol and ERC721.sol have been rewritten to use openzeppelin standards.
• Move tester contracts (LoadTester.sol and ConformanceTester), as well as go files used to test precompiles and other stuff, to the tester package.
• Add new CI job to make sure abi, bytecode and go binding files are up to date (it'll also test if the contracts can be built using forge)

Jira / Linear Tickets

• DVT-1075 fix: ERC20 bytecode deployment
• DVT-1117 chore: transform the contracts repository into a forge repository

Testing

• Deploy ERC20 smart contract from bytecode.

# previously
$ cast send \
    --from 0x85dA99c8a7C2C95964c8EfD687E95E632Fc533D6 \
    --private-key 0x42b6e34dc21598a807dc19d7784c71b2a7a01f6480dc6f58258f78e539f1a1fa \
    --rpc-url localhost:8545 \
    --json \
    --create \
    "$(cat ./contracts/tokens/ERC20/ERC20.bin)" | jq
Error: 
(code: -32000, message: execution reverted, data: None)

# now
$ cast send \
    --from 0x85dA99c8a7C2C95964c8EfD687E95E632Fc533D6 \
    --private-key 0x42b6e34dc21598a807dc19d7784c71b2a7a01f6480dc6f58258f78e539f1a1fa \
    --rpc-url localhost:8545 \
    --json \
    --create \
    "$(cat ./contracts/src/tokens/ERC20.bin)" | jq
✅

• go run main.go loadtest --mode erc20 --verbosity 600 --requests 100 --rate-limit 100
• go run main.go loadtest --mode erc721 --verbosity 600 --requests 100 --rate-limit 100
• go run main.go loadtest uniswapv3 --verbosity 600 --requests 100 --rate-limit 100
• go run main.go rpcfuzz --verbosity 600
• go run main.go loadtest --mode random --verbosity 600 --requests 100 --rate-limit 100

[praetoriansentry]

Definitely seems a little odd to see src in a package name, but I think overall this is fine.