[gwyneth] Add rbuilder to Dockerfile of EL

[adaki2004]

No description provided.

[adaki2004]

@Brechtpd some TLDR for you.

This PR basically does nothing else just trying to incorporate the rbuilder into the workflow.

We have an rbuilder repo under taiko's organization. During every EL image creation (and then manage and run it by kurtosis with make install ) we:

• clone the repo into the container + build an executable binary from rbuilder.

Currently, you can run the builder by:
rbuilder run /app/config-gwyneth-reth.toml (you need to make always some mods to the config file, but instructions written there, before you run it).

It seems to be working (to some extent) because at least it detects somehow every blocks. Still not great because if i send txn to the L2 rpc, with : python3 sendTx.py -p 51566 -> new payload starts, consensus will build the block and execution layer executes BUT at least rbuilder detects a new block !
You can see in green, this kind of message is appearing when new block is detected by rbuilder:

Obviously we want to stop this "create new L2 block per every L2 send_rewTransaction to our node"? but currently here we are.

To go further on the rbuilder path, why it does not prints out my debug message (in commit_tx()) (this is in the rbuiluder repo obviously) shall be i guess the next steps.

[adaki2004]

@Brechtpd

You can use blockscout is deployed for L1 and L2. And you can verify contracts now, after deployment.

L1 deployment and verification (in 1 command):
forge script ./scripts/DeployOwnerExample.s.sol --rpc-url http://localhost:51986 --broadcast --verify --verifier blockscout --verifier-url http://localhost:52010/api --legacy --private-key "YOUR_PK"

For L2 obviously how the rbuilder currently puts together a block and proposes it.
But just leaving it here as an example, a separate verification-only command:
forge verify-contract 'XY' contracts/examples/OwnerExample.sol:Owner --watch --verifier-url "http://localhost:52024/api" --verifier blockscout --chain-id YOU_CHAIN_ID