CI for mesa

[dkijania]

Adding CI for mesa :

• building noble and bookwom for devnet and lightnet profile for amd64 and arm64 architectures
• tagged applicable jobs with Mesa tag - here my goal was to not run all other building jobs like we do for devnet/mainnet. Currently Mesa is at bugs exploration path, so we don't need to support every configuration. This is not needed now. But i want to use this branch as new method of filtering jobs per mainline branch. We need to bring back those deleted jobs anyhow
• regenerated archive static test data for mesa
• cherry picked https://github.com/MinaProtocol/mina/pull/18159 to stability

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

Nightly: https://buildkite.com/o-1-labs-2/mina-end-to-end-nightlies/builds/4016

[dkijania]

!ci-docker-me codename=bookworm arch=amd64 profile=devnet

[dkijania]

!ci-docker-me codename=bookworm arch=amd64 profile=lightnet

[dkijania]

!ci-docker-me codename=bookworm arch=arm64 profile=devnet

[dkijania]

!ci-docker-me codename=bookworm arch=amd64 profile=lightnet

[dkijania]

!ci-docker-me codename=bookworm arch=amd64 profile=lightnet

[dkijania]

!ci-docker-me codename=bookworm arch=armd4 profile=lightnet

[dkijania]

!ci-docker-me codename=bookworm arch=amd64 profile=devnet

[dkijania]

!ci-docker-me codename=bookworm arch=arm64 profile=lightnet

[glyh]

We will merge mesa back to develop in the end I assume. There's some destructive changes in this repo. What's the plan to deal with them in the future?

[dkijania]

@glyh the plan is to work on dhall filtering and make it common for all branches,before merging to develop. So this branch should only contains ports from compatible for patching issues we are having right now.

I choose that strategy as issues on mesa CI are not directly connected with branch but with limitations of CI which were exposed here

[glyh]

So the files that would be removed when merging back to develop is expected, or it's a WIP?

[dkijania]

!ci-docker-me codename=bookworm arch=arm64 profile=lightnet

[dkijania]

So the files that would be removed when merging back to develop is expected, or it's a WIP?

I thought we want this branch quickly to be run in CI. Thus my hacky approach. If not, then i can sort it out longterm

[dkijania]

!ci-docker-me codename=bookworm arch=arm64 profile=devnet

[dkijania]

!ci-docker-me codename=bookworm arch=amd64 profile=devnet

[dkijania]

!ci-docker-me codename=bookworm arch=amd64 profile=lightnet

[dkijania]

!ci-docker-me codename=bookworm arch=amd64 profile=lightnet

[glyh]

I assume this is not yet ready for a review? If so could you draft?