feat: support local prover && multiple task types

[yiweichi]

1. Support local prover
2. Support multiple task types in one prover process

[georgehao]

Actually, I think we should combine this repo and prover repo to small one, let this repo become a crate of prover. wdyt @Thegaram

the layout maybe like this

prover
---- cargo.toml
        cargo.lock
        crates
           ----  wrapper ( contains coordinator client, geth client, circuit, etc)
           ----  local
           ----  remote  

[georgehao]

for the easily usage, we should simpfy some config option like n_workers http option, we should have a default value for it, ane make it to a optional field.

[Thegaram]

Why are these two merged into one?

[yiweichi]

that's a lagacy from coordinator's side. we used to not split batch prover and bundle prover. So from coordinator's view, there are only 2 types of prover (chunk prover and batch prover).

[Thegaram]

Do we spin up n workers that each can support all prover types?

[yiweichi]

Yes, that's true. but we can also spin up n workers that can only prove batch or chunk.

[Thegaram]

Side note: Once this is merged, please submit a PR to https://github.com/Sindri-Labs/sindri-scroll-sdk (should be just a few simple fixes).

[Thegaram]

Actually, I think we should combine this repo and prover repo to small one, let this repo become a crate of prover

We discussed this offline, but just so that we have info here:

• This repo (https://github.com/scroll-tech/scroll-proving-sdk) is supposed to be the wrapper part.
• local should be in the monorepo. Ideally all local-specific stuff (like local config) should be there and not in this repo.
• remote will be implemented by 3rd-parties, e.g. https://github.com/Sindri-Labs/sindri-scroll-sdk