Introduce a zero install transport for learning and demos

[andreasohlund]

This adds a file disk based transport optimized for a good first development experience.t

This allow us to:

• Unlock all samples from MSMQ since most of them can use the dev transport instead and only a few needs to be transport specific
• It's like cassini was to IIS, allows you to get going without having to install infrastructure
• Allows us to take persitence out of the picture for new starters since timeouts can be handled by the dev transport
• Allows the other transports to optimize for production readiness by not containing "f5 experience" workarounds in them, example here are the retries MSMQ does when subscriptions are sent to non existing queues. This also applies to the core where we wouldn't have to run installers since the dev transport could set everything up always
• We can take routing out of the picture since the dev transport can (not yet done) handle both pub sub and plain sends with 0 config.
• We can propagate the knowledge that a dev transport is in use to allow dowstreams to adjust accordingly
• When doing support cases we can send code samples that is transport agnostic without knowning what transport they are on
• This allows msmq to be moved out of the core and therefore unlock us to support dot net core
• No longer needed for the Platform installer to install MSMQ
• Gives us a transport in the core that can drive the acceptance tests both form message driven pubsub and native pub sub (since we can support both)

[andreasohlund]

Assigned to the 6.3 milestone

[andreasohlund]

This is now done