Include tests that depend on linked libraries in Foundry devchain integration test

[arthurgousset]

In Foundry integration tests (for the devchain), we cannot test contracts that depend on linked libraries because vm.getDeployedCode() cannot fetch bytecode of contracts that depend on linked libraries. This is a known limitation of Foundry at the moment.

They merged a PR that fixes this:

• Issue: https://github.com/foundry-rs/foundry/issues/6120
• PR: https://github.com/foundry-rs/foundry/pull/8034
• Release: nightly-fbad377ab26a432e48444cf324feee1195a30960

Unfortunately, we can't use the latest version, because of a regression it has in finding artifacts, which is a known issue:

• https://github.com/smartcontractkit/foundry-chainlink-toolkit/issues/15

As soon we can bump the version, it might be good to include contracts that depend on linked libraries in the tests.

Practically, this would simply involve removing this if-clause:

https://github.com/celo-org/celo-monorepo/blob/c27a53eaf1cd5729e1b785e90051eac3fb821184/packages/protocol/test-sol/integration/Integration.t.sol#L47-L58

Originally encountered this limitation in this PR:

• https://github.com/celo-org/celo-monorepo/pull/11002#discussion_r1626302484

[arthurgousset]

This is is blocked by a regression introduce in the latest foundry version. As a next step, I'd like to make sure a bug is filed or add a comment to an existing but report, so this can be fixed in a future release)