feat: add p2p crate

[Rjected]

adding reth-p2p based on the template for now, this should eventually provide nice interfaces for other components to interact with the network.

[mattsse]

should we move this into a subfolder called net?
so ./net/p2p or ./net/devp2p?

I can imagine we'll need additional stuff related to p2p, or net in general

[Rjected]

yeah, there will probably be multiple crates related to networking (sentry? downloader?) so that makes sense

[onbjerg]

nit: let's make a habit of writing docs "normal cased"(? is that even a term), so e.g. "networking utilities for reth" -> "Networking utilities for reth"

[mattsse]

I don't think we need to make net a crate itself.

Suggested change

	[package]
	name = "reth-net"
	version = "0.1.0"
	edition = "2021"
	license = "MIT OR Apache-2.0"
	repository = "https://github.com/foundry-rs/reth"
	readme = "README.md"
	description = "networking utilities for reth"
	[dependencies]

[Rjected]

afaik cargo doesn't support workspace members without a Cargo.toml, so either we need net as a crate or we would have to specify the subfolders (net/p2p) as individual workspaces. Maybe we can go back to this as p2p and see if the hierarchy makes more sense once more networking related code has been written

[mattsse]

this only works if we're explicitly setting members:

     "crates/primitives",
    "crates/net/p2p",

instead of crates/*

I suggest we just list all crates that we have

[Rjected]

I see, that makes sense. switched to explicitly setting workspace members

[mattsse]

if we need a utils/common crate for net we can just create /net/utils