ci: devnet setup with curio

[lemmih]

Summary of changes

Changes introduced in this pull request:

• Basic devnet with Curio + Forest.
• Mining does not yet work with Forest. This will be addressed in subsequent PRs.
• This devnet setup is not tested in CI since mining doesn't yet work.

Reference issue to close (if applicable)

Part of #4716

Other information and links

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

[LesnyRumcajs]

I'd usually do ❯ docker compose down --rmi all -v to be thorough.

[LesnyRumcajs]

It might be worth noting that it's a copy of the same script from the devnet compose.

[lemmih]

The Curio devnet will eventually replace the lotus-miner devnet, right? So, eventually, we'll only have a single copy of the file.

[ruseinov]

looks good to me!

some non-blocking nits

[LesnyRumcajs]

Does it have to be copied? Can we point to the existing files in the devnet/?

[LesnyRumcajs]

Same applies for some of the other files, e.g., Lotus dockerfile or check.sh.

[lemmih]

I don't think files should be shared between the two devnet configurations.

[LesnyRumcajs]

Do you expect those dockerfiles to be differ in the future? All in all, those are just regular builds for 2k networks.

[LesnyRumcajs]

That said, it might make more sense to put them in a common directory. We can do it in a follow-up. All in all, if possible, I'd like to avoid duplication.