[Feature]: Wire up BlockObserver in the main entrypoint

[cylewitruk]

Feature - Wire up BlockObserver in the main entrypoint

1. Description

The BlockObserver needs to be wired-up and its runloop run in the main event loop.

1.1 Context & Purpose

The BlockObserver is a dependency for both the TransactionSigner and the TransactionCoordinator and needs to be running prior to either of these being started (they are dependent on its messaging channels).

2. Technical Details:

The BlockObserver itself has several dependencies which also need to be wired up:

• BitcoinInteract + BitcoinClient
• EmilyClient (which I think should be changed to EmilyInteract)
• StacksClient (which I think should be changed to StacksInteract)
• Bitcoin blockhash stream (from zmq)
• ✅ P2P network

Then it also takes a watch channel for informing the application of database updates, which need to be centralized somehow so that the TransactionSigner and TransactionCoordinator instances can use it. This should probably be updated to use the app signalling channel instead with a proper message type to promote decoupling.

2.1 Acceptance Criteria:

• The BlockObserver can be created with all of its dependencies
• All required dependencies for the TransactionSigner and TransactionCoordinator are available for them to be created.
• The BlockObserver correctly runs and can process events in the dev environment.