New ST spec for publishing to multiple nodes

[jeremydmiller]

Replace:

Send a single message to multiple listening nodes
    Website1
        Listens to memory://harness/website1 with 
        Listens to memory://localhost/Website1/replies with 
        Publishes to Harness:Service1
            * OneMessage
        Publishes to Harness:Service3
            * OneMessage
        Handles Message, JobRequest`1, JobRequest`1, JobRequest`1, JobRequest`1, SubscriptionRequested, SubscriptionsChanged, SubscriptionsRemoved, TakeOwnershipRequest, TaskHealthRequest, TaskDeactivation

    Service1
        Listens to memory://harness/service1 with 
        Listens to memory://localhost/Service1/replies with 
        Handles OneMessage, Message, JobRequest`1, JobRequest`1, JobRequest`1, JobRequest`1, SubscriptionRequested, SubscriptionsChanged, SubscriptionsRemoved, TakeOwnershipRequest, TaskHealthRequest, TaskDeactivation

    Service2
        Listens to memory://harness/service2 with 
        Listens to memory://localhost/Service2/replies with 
        Handles OneMessage, Message, JobRequest`1, JobRequest`1, JobRequest`1, JobRequest`1, SubscriptionRequested, SubscriptionsChanged, SubscriptionsRemoved, TakeOwnershipRequest, TaskHealthRequest, TaskDeactivation

    Service3
        Listens to memory://harness/service3 with 
        Listens to memory://localhost/Service3/replies with 
        Handles OneMessage, Message, JobRequest`1, JobRequest`1, JobRequest`1, JobRequest`1, SubscriptionRequested, SubscriptionsChanged, SubscriptionsRemoved, TakeOwnershipRequest, TaskHealthRequest, TaskDeactivation

    Service4
        Listens to memory://harness/service4 with 
        Listens to memory://localhost/Service4/replies with 
        Handles OneMessage, Message, JobRequest`1, JobRequest`1, JobRequest`1, JobRequest`1, SubscriptionRequested, SubscriptionsChanged, SubscriptionsRemoved, TakeOwnershipRequest, TaskHealthRequest, TaskDeactivation


    Actions
        Node Website1 sends new message of type OneMessage (first message)
    Messages are all accounted for

    Assertions
        Message of type OneMessage (first message) should be received by Service1
        Message of type OneMessage (first message) should be received by Service3

    Messages Received
    * OneMessage received by memory://harness/service3
    * OneMessage received by memory://harness/service1