feat(da-clients): add Celestia client

[dimazhornyk]

What ❔

This PR adds a Celestia DA client.
The main complexity of this PR comes from our goal to lower the operational load and not run the Celestia light node (which is a default way of interacting with Celestia blockchain).

This was done by adapting Astria's Celestia client implementation to our codebase and removing unneeded logical components.

Note that Celestia's main communication protocol is gRPC, which means we have to import or maintain the proto definitions. I decided to reuse the generated .rs files from Astria's repo to remove the need to maintain the .proto files in our repo (not the cleanest way, but consider it a rather temporary solution).
There is a celestia-proto crate that has all the codegen that we need, but they don't generate the gRPC client definitions, only the types, so we can't use them atm. I will try to ask the team maintaining it to add such an option, then we would be able to remove all the codegen from our repo, and simply import it from celestia-proto.

Example config:

da_client:
  celestia:
    api_node_url: http://grpc-mocha.pops.one:9090
    namespace: 000000000000000000000000000000000000ca1de12a5e2d5beb9ba9
    chain_id: mocha-4
    timeout_ms: 10000

secrets:

da:
  celestia:
    private_key: PRIVATE_KEY_WITHOUT_0x_PREFIX

Why ❔

To enable Celestia DA in ZK stack

Checklist

• PR title corresponds to the body of PR (we generate changelog entries from PRs).
• Tests for the changes have been added / updated.
• Documentation comments have been added / updated.
• Code has been formatted via zk fmt and zk lint.

[zvolin]

There is a celestia-proto crate that has all the codegen that we need, but they don't generate the gRPC client definitions, only the types, so we can't use them atm. I will try to ask the team maintaining it to add such an option, then we would be able to remove all the codegen from our repo, and simply import it from celestia-proto.

Hey, we should be able to add this to celestia-proto, maybe behind some feature flag 🤔. It would be cool if you could open us an issue providing further details, which grpcs are needed, and how you would want those generated (tonic?)

[perekopskiy]

Looks good. I see that compilation for unit tests increased from 9 to 11 minutes in this PR but in PR with eigen where tonic default features are removed it's 10 minutes, so it's a ~10% increase in the end (9min->10min). IMO 10% is acceptable in this case.

[github-actions]

Detected VM performance changes

Benchmark name	Est. cycles	Change in est. cycles
init/fast	9145099	+4.5%