Stream definitions should not be saved when auto-deploy results in an error

This relates to XD-871 which provides a good scenario.

>stream create s1 --definition "http | log --deploy"
>stream create s2 --definition "http | log --deploy"

The second command results in an error message that the port is in use but the stream definition is still saved. Since create + deploy is a logical unit of work, it should follow transactional semantics. In other words if the deploy fails, the repository should be rolled back (or a compensating destroy should be performed). Note this should not be handled the same way if create and deploy happen separately. In that case, the stream definition should remain.