change(rpc): Adds a TrustedChainSync struct for keeping up with Zebra's non-finalized best chain from a separate process

[arya2]

Motivation

This is an early draft for making the ReadStateService more usable from a separate process. This PR will likely go through large changes before it merges, there are still many TODOs left and it's missing tests.

Closes #8580.
Closes #8576.
Closes #8520.

PR Author Checklist

Check before marking the PR as ready for review:

• Will the PR name make sense to users?
• Does the PR have a priority label?
• Have you added or updated tests?
• Is the documentation up to date?

For significant changes:

• Is there a summary in the CHANGELOG?
• Can these changes be split into multiple PRs?

If a checkbox isn't relevant to the PR, mark it as done.

Solution

Adds a TrustedChainSync struct for getting non-finalized blocks from a Zebra RPC server and sending new blocks to the ChainTipSender to be usable by ChainTipChange in zebra-scan and elsewhere.

Testing

This PR still needs tests.

Review

Anyone can review, @oxarbitrage may be interested.

Reviewer Checklist

Check before approving the PR:

• Does the PR scope match the ticket?
• Are there enough tests to make sure it works? Do the tests cover the PR motivation?
• Are all the PR blockers dealt with?
  PR blockers can be dealt with in new tickets or PRs.

And check the PR Author checklist is complete.

[arya2]

@oxarbitrage this file is probably the most ready for review and would benefit most from suggestions, other files would probably be easier to review after some clean up.