The "All messages" default Stream is somehow special, and installing a Content Pack that has it in the entity list should not create a new Stream for it, but use the existing one.
Current Behavior
Installing a Content Pack that has the "All messages" Stream as dependency creates a new "All messages" Stream, that does not behave in the same way as the original one.
That affects Pipelines that may need to be applied into all messages, and specially Dashboard Widgets created against the Stream. The latter case is specially bad, because we don't let users alter the Stream after the Widget was created.
Expected Behavior
The "All messages" default Stream is somehow special, and installing a Content Pack that has it in the entity list should not create a new Stream for it, but use the existing one.
Current Behavior
Installing a Content Pack that has the "All messages" Stream as dependency creates a new "All messages" Stream, that does not behave in the same way as the original one.
That affects Pipelines that may need to be applied into all messages, and specially Dashboard Widgets created against the Stream. The latter case is specially bad, because we don't let users alter the Stream after the Widget was created.
Example of content pack having this issue: v2.txt
Steps to Reproduce (for bugs)
Your Environment