[kurtosis] create an eigenda kt-devnet that uses proxy with memstore instead of talking to holesky-eigenda

[samlaf]

For insecure integrations, it's not clear that we gain much from using the eigenda network as opposed to just a proxy with memstore.

For secure integrations (where settlement needs to happen on same chain that eigenda verifies certs), we would either need to:

1. deploy eigenda on local ethereum-package chain
2. or make the op-package point to holesky

[samlaf]

Just need to create a new eigenda-memstore-devnet.yaml file similar to our eigenda-holesky-devnet.yaml that starts proxy with memstore flags instead of eigenda flags.