Forward validations and manifests in reporting mode

[natenichols]

High Level Overview of Change

Forwards validations and manifest subscription streams in reporting mode.

Context of Change

In order for reporting mode to be deployed to s1 and s2, it must support subscriptions to the validations and manifests streams.

This PR adds those streams in the same manner as transactions_proposed. validationReceived and manifestReceived messages are forwarded from the ETL Source to subscribers.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking change that only restructures code)
• Tests (You added tests for code that already exists, or your new feature included in this PR)
• Documentation Updates
• Release

[cjcobb23]

Looks good, did you test this at all?

[natenichols]

Yea, set it up locally and tried out the validations stream. Still need to test out the manifests

[cjcobb23]

Can we hook it up to the validations-mainnet bot and make sure everything works correctly?

[natenichols]

Sure, do you have an instance running anywhere? Or should I just set that up locally?

[cjcobb23]

I don't have an instance; is it a pain to setup locally?

[natenichols]

nah I just might not get to it til next week

[cjcobb23]

I tested this. Everything looks good.

[mtrippled]

Update the documentation for this function which currently only describes the transaction stream.

[mtrippled]

Do the shouldPropagateStream() check once instead of in 3 places. Then, if the check passes, check for each of the stream types and proceed accordingly.

This removes duplicated code and I think makes the intention more clear.

[mtrippled]

LGTM 👍