This is a test run, to see how `setUp()` and contract definitions work.

1. run devchain

```sh
./migrations_sol/create_and_migrate_anvil_devchain.sh
```

2. run test against devchain

```sh
forge test \
--match-path test-sol/integration/Integration.t.sol \
--match-contract GoldTokenTest_General \
-vvv \
--fork-url http://127.0.0.1:8546
```

Tests pass

Output:

```sh
[⠰] Compiling...
No files changed, compilation skipped

Running 3 tests for test-sol/integration/Integration.t.sol:GoldTokenTest_General
[PASS] test_decimals() (gas: 10837)
Logs:
  GoldToken address is: 0xfE8CbC1cFA1b3b8256f310bdfd40E60597083448

[PASS] test_name() (gas: 12537)
Logs:
  GoldToken address is: 0xfE8CbC1cFA1b3b8256f310bdfd40E60597083448

[PASS] test_symbol() (gas: 12579)
Logs:
  GoldToken address is: 0xfE8CbC1cFA1b3b8256f310bdfd40E60597083448

Test result: ok. 3 passed; 0 failed; 0 skipped; finished in 135.40ms

Ran 1 test suites: 3 tests passed, 0 failed, 0 skipped (3 total tests)
```

This is to allow me to use the `.code` property on deployed smart contracts, which is only supported on Solidity 0.8 and above.

In Solidity versions 0.7.0 and later, constructors are implicitly internal, meaning they can only be called within the contract itself or derived contracts, making the visibility keyword redundant.

The state mutability of a function can be restricted to view if the function does not modify the state of the blockchain. A view function promises not to alter the state, which allows the Ethereum Virtual Machine (EVM) to optimize how it handles the function.

The function does not modify any state; it only reads from the registry and logs some information.

…ecode

The goal is to use that in both the migration script (`Migration.s.sol`) and the integration test (`Integration.t.sol`).

….sol`

Mistakenly deleted earlier

Also adds docstring for better readability.

… test

…itly

…com:celo-org/celo-monorepo into arthurgousset/chore/anvil-integration-tests

The latest version has a regression that leads to a failing integration test. But, fixing a previous nightly build fixed the error.

Because I'm downgrading to a previous foundry version, I have to undo the change to this line made in this PR: #10997

I always forget to run `yarn prettify` in the top-level directory

To explain what flags and arguments are used.

Using `yarn prettify` in the top-level directory

Adds function in `Integration.t.sol` directly to avoid 0.5.x version problems.

…r function

Because the script is now on 0.8, we can use the `.code` property to fetch the runtime bytecode of a smart contract deployed on the devchain. Previously, we needed to load the bytecode from storage with inline assembly.

Functionally this should be the same, but the configs and flags are more readable.