Initial project structure

[rach-id]

As per the sync with @rahulghangas and @evan-forbes , we could start off with the following project structure:

cmd->
    -> orchestrator:  config + cmd
    -> relayer
    -> deployer
    -> verifier

evm -> will contain all the EVM related code

orchestrator ->  will contain the signing parts, and the go routines doing: listening for new attestations, calling the signer ...

p2p -> P2P related code 

relayer -> will contain the relayer querying the QGB smart contract, creating EVM transactions, submitting them

store -> which will contain the implementation for the confirms store (and probably the attestations..)

types-> should contain the ValsetConfirm and DataCommitmentConfirm messages + their corresponding methods:

For the types, they could be as follows:

// DataCommitmentConfirm describes a data commitment for a set of blocks.
type DataCommitmentConfirm struct {
	// Universal nonce referencing the Data Commitment.
	Nonce uint64
	// Signature over the commitment, the range of blocks, the validator address
	// and the Ethereum address.
	Signature string
	// Orchestrator account address who will be signing the message.
	ValidatorAddress string
	// Hex `0x` encoded Ethereum public key that will be used by this validator on
	// Ethereum.
	EthAddress string
	// Merkle root over a merkle tree containing the data roots of a set of
	// blocks.
	Commitment string
	// First block defining the ordered set of blocks used to create the
	// commitment.
	BeginBlock uint64
	// Last block defining the ordered set of blocks used to create the
	// commitment.
	EndBlock uint64
}