Server restart with streams sourced/mirrored could produce warnings

[derekcollison]

Defect

If a source stream S1 is sourced by S2, but the server recovers them in reverse order, S2 could try to create the internal consumer to S1 before it is recovered, causing warnings to be printed. I believe this is benign since we will retry, but be good to cleanup.

We already recover streams first then consumers that were created by external sources, but in this case its an internal and ephemeral/direct that is controlled by S2.

Simple fix would be to filter any stream on recover that is a downstream source or mirror and do those in a second stage.

Thanks to @aricart for the report.

[derekcollison]

These are benign as the system will retry periodically.