EPIC: Bridge integration

[cmwaters]

This issue tracks the design and possible implementation of embedding the bridge node system within the consensus node (given that these processes are intended to run in tandem). The listed benefits of a complete solution here are:

• Decreased computation:
  • Only a single construction of the EDS and DAH (as opposed to once within consensus and once within the bridge)
  • No need to verify headers, commits and other data (as they have already been verified by the consensus node)
• A single storage solution
  • Reduction of the duplication of data
  • Cache layering system for EDS, ODS, Block, State-mutating transactions (this needs to be scoped out with a corresponding consolidated syncing solution that both core and node can use)
• Remove reliance on flaky RPC layer
  • Error handling, retries. Problems with batch requests and dropping of responses under load
• An improved UX
  • Node operators have a single binary and a unified convention to running them
  • A single process to manage consensus and the serving of data to the DA layer

For Admin Use

• [ ] Not duplicate issue
• [ ] Appropriate labels applied
• [ ] Appropriate contributors tagged
• [ ] Contributor assigned/self-assigned

[cmwaters]

Higher level reference: https://github.com/celestiaorg/celestia-app/pull/2745