added profile and services for hemitrap in testnet

[ClaytonNorthey92]

Summary

• added a new profile in the testnet docker compose called "hemitrap". this profile sets up a forked network of our testnet to test deploying smart contract updatest, then running localnet tests against them
• there is explicitly no README added; this is simply a new docker compose profile to be used by the greater ecosystem

Changes
see summary.

[joshuasing]

Question - Do we want to do this as a part of the existing docker-compose file(s)? Would this potentially be better to implement as separate compose files to avoid accidental use? 🤔

[ClaytonNorthey92]

@joshuasing it shares volumes with the original compose file, namely the op-geth-l2 volumes (geth and tbc). so it would be easiest to have it in the same file.

the steps are:

• sync a node
• stop the synced node
• run the hemitrap profile

it will pick up where that synced node left off and work on its own fork

[jcvernaleo]

You need to add this to the documentation.

[ClaytonNorthey92]

You need to add this to the documentation.

@jcvernaleo added 👍 let me know if you want me to add anything else

[joshuasing]

Please pin this to a specific tag and sha256 digest:

Suggested change

	image: ghcr.io/foundry-rs/foundry:latest
	image: ghcr.io/foundry-rs/foundry:v1.4.1@sha256:629bebb49d1ba44a52a9fc14229dd58930e3193b4b206ae43ad00089e9ead95b

[joshuasing]

This doesn't seem to have been resolved

[jcvernaleo]

My concern was covered so I'm hitting approve but looks like @joshuasing's may not be addressed yet and I do think those are important too (the docker image ones in particular.