Refactor project structure to accommodate tests, and better management

[SkandaBhat]

The project can be refactored using crate to better manage features and to setup end to end tests to validate spec.

Current project structure:

src/chainspec.rs
src/evmconfig.rs
src/execute.rs
src/node.rs
...

Proposed structure:

bin/
crates/
crates/e2etests/
crates/node/
crates/evm/
...

Inspiration: https://github.com/ithacaxyz/odyssey

op reth also has a very similar structure: https://github.com/paradigmxyz/reth/tree/main/crates/optimism

[dapplion]

Why not, I wasn't worrying too much about the organization since the project is pretty early. @debjit-bw thoughts?

[SkandaBhat]

Biggest reason I would advocate for this is that spec tests will get easier to setup, and the effort to do this is quite low. I can create a draft and see if it makes sense

[debjit-bw]

Individual features like payload builder or evm are too small to make their independent crates, I feel. We can have one crate with whole reth_gnosis, and one for testing maybe.