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: Support library linking in vm.getDeployedCode foundry-rs/foundry#6120
• PR: refactor: deploy all libraries when running tests foundry-rs/foundry#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:

• No matching artifact found smartcontractkit/foundry-chainlink-toolkit#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:

celo-monorepo/packages/protocol/test-sol/integration/Integration.t.sol

Lines 47 to 58 in c27a53e

	// Skipping test for contracts that depend on linked libraries
	// This is a known limitation in Foundry at the moment:
	// Source: https://github.com/foundry-rs/foundry/issues/6120
	if (
	hashContractName != hashAccount &&
	hashContractName != hashElection &&
	hashContractName != hashEscrow &&
	hashContractName != hashFederatedAttestations &&
	hashContractName != hashGovernance &&
	hashContractName != hashSortedOracles &&
	hashContractName != hashValidators
	) {

Originally encountered this limitation in this PR:

• test: add integration tests for Anvil migrations #11002 (comment)

[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)