Include the snippets in the docs

Author: SzymonPobiega

Snippets/ASBS/ASBS_5/Usage.cs

@@ -4,6 +4,9 @@
 using Azure.Identity;
 using Azure.Messaging.ServiceBus;
 using NServiceBus;
+using NServiceBus.Transport;
+using NServiceBus.Transport.AzureServiceBus;
+using Shipping;
 
 class Usage
 {
@@ -62,15 +65,7 @@ class Usage
 
         using var stream = File.OpenRead("topology-options.json");
         var options = JsonSerializer.Deserialize<TopologyOptions>(stream, TopologyOptionsSerializationContext.Default.Options);
-        var topology = TopicTopology.FromOptions(options);
-
-        #endregion
-
-        #region asb-options-options-loading
-
-        using var stream = File.OpenRead("topology-options.json");
-        var options = JsonSerializer.Deserialize<TopologyOptions>(stream, TopologyOptionsSerializationContext.Default.Options);
-        var topology = TopicTopology.FromOptions(options);
+        var jsonTopology = TopicTopology.FromOptions(options);
 
         #endregion
 

transports/azure-service-bus/configuration_entity-topology_asbs_[5,).partial.md

@@ -18,6 +18,18 @@ The following snippet demonstrates raw deserialization of options and creating t
 
 snippet: asb-options-options-loading
 
+The topology json document for the topic-per-event topology looks following:
+
+snippet: topology-options
+
+In order to support polymorphic events, one event (base type) can be mapped to multiple topics (where the derived events are published):
+
+snippet: topology-options-inheritance
+
+Loading from json is also supported for the migration topology:
+
+snippet: migration-options
+
 ##### Validation
 
 During the start of the transport the topology configuration is validated against some of the well known limitations like entity, subscription or rule name lengths and some consistency validation is executed.