chore(naming): use '.ServiceBus' postfix in new namespace

Author: stijnmoreels

docs/preview/02-getting-started.md

@@ -36,7 +36,7 @@ The package makes the `IServiceBusMessageHandler<>` interface available. Impleme
 As the generic type, you can use the DTO (data-transfer object) to which the [`ServiceBusReceivedMessage.Body`](https://learn.microsoft.com/en-us/dotnet/api/azure.messaging.servicebus.servicebusreceivedmessage.body) should be deserialized to (default via JSON). In this case: `MyOrder`.
 
 ```csharp
-using Arcus.Messaging;
+using Arcus.Messaging.ServiceBus;
 
 public class MyOrder
 {

docs/preview/03-Features/01-Azure/01-service-bus.mdx

@@ -23,7 +23,7 @@ To receive the Azure Service Bus message in a deserialized form, you can impleme
 Here is an example of such a message handler that expects messages of type `Order`:
 
 ```csharp
-using Arcus.Messaging;
+using Arcus.Messaging.ServiceBus;
 
 public class Order
 {
@@ -236,7 +236,7 @@ It is a good practice as application developer to dead-letter the message yourse
 :::
 
 ```csharp
-using Arcus.Messaging;
+using Arcus.Messaging.ServiceBus;
 
 public class OrderMessageHandler : IServiceBusMessageHandler<Order>
 {
@@ -267,7 +267,7 @@ When your message handler interacts with an external dependency, that dependency
 To interact with the message processing system within your *message handler*, you can inherit from the `CircuitBreakerServiceBusMessageHandler<>`, which allows you to 'enrich' your handler with circuit-breaker functionality.
 
 ```csharp
-using Arcus.Messaging;
+using Arcus.Messaging.ServiceBus;
 
 // highlight-next-line
 public class OrderMessageHandler : DefaultCircuitBreakerServiceBusMessageHandler<Order>

docs/preview/03-Guides/migration-guide-v3.0.md

@@ -50,9 +50,9 @@ All Azure EventHubs-related functionality has been removed from v3.0. This means
   * `ServiceBusReceivedMessage.GetApplicationProperty`
   * `MessageContext.GetMessageEncodingProperty`
 ### ✏️ Renamed functionality
-* Renamed `IAzureServiceBusMessageHandler<>` to `IServiceBusMessageHandler<>` (in namespace `Arcus.Messaging`)
-* Renamed `AzureServiceBusMessageContext` to `ServiceBusMessageContext` (in namespace `Arcus.Messaging`)
-* Renamed `CircuitBreakerServiceBusMessageHandler<>` to `DefaultCircuitBreakerServiceBusMessageHandler<>` (in namespace `Arcus.Messaging`)
+* Renamed `IAzureServiceBusMessageHandler<>` to `IServiceBusMessageHandler<>` (in namespace `Arcus.Messaging.ServiceBus`)
+* Renamed `AzureServiceBusMessageContext` to `ServiceBusMessageContext` (in namespace `Arcus.Messaging.ServiceBus`)
+* Renamed `CircuitBreakerServiceBusMessageHandler<>` to `DefaultCircuitBreakerServiceBusMessageHandler<>` (in namespace `Arcus.Messaging.ServiceBus`)
 
 ### ✨ New Service Bus message pump registration
 Previously, the registration of the Azure Service Bus message pump involved navigating through the many available extensions, making it rather tedious to find the right authentication mechanism.
@@ -108,6 +108,8 @@ Previous versions used dedicated 'template classes' that custom message handlers
 Starting from v3.0, the available operations are moved to the `ServiceBusMessageContext` (previously called `AzureServiceBusMessageContext`). Making your custom message handlers much more accessible and flexible.
 
 ```diff
++ using Arcus.Messaging.ServiceBus;
+
 public class OrderServiceBusMessageHandler
 -    : AzureServiceBusMessageHandler<Order>
 +    : IServiceBusMessageHandler<Order>

src/Arcus.Messaging.Abstractions.ServiceBus/AzureServiceBusMessageContext.cs

@@ -5,9 +5,10 @@
 using System.Threading.Tasks;
 using Arcus.Messaging.Abstractions;
 using Arcus.Messaging.Abstractions.ServiceBus;
+using Arcus.Messaging.ServiceBus;
 using Azure.Messaging.ServiceBus;
 
-namespace Arcus.Messaging
+namespace Arcus.Messaging.ServiceBus
 {
     /// <summary>
     /// Represents the contextual information concerning an Azure Service Bus message.

src/Arcus.Messaging.Abstractions.ServiceBus/Extensions/ServiceBusMessageHandlerExtensions.cs

@@ -5,6 +5,7 @@
 using Arcus.Messaging.Abstractions.MessageHandling;
 using Arcus.Messaging.Abstractions.ServiceBus;
 using Arcus.Messaging.Abstractions.ServiceBus.MessageHandling;
+using Arcus.Messaging.ServiceBus;
 using Microsoft.Extensions.Logging;
 
 // ReSharper disable once CheckNamespace

src/Arcus.Messaging.Abstractions.ServiceBus/Extensions/ServiceBusMessageHandlerOptions.cs

@@ -1,9 +1,9 @@
 using System;
 using System.Collections.ObjectModel;
 using System.Linq;
-using Arcus.Messaging;
 using Arcus.Messaging.Abstractions.MessageHandling;
 using Arcus.Messaging.Abstractions.ServiceBus;
+using Arcus.Messaging.ServiceBus;
 using Azure.Messaging.ServiceBus;
 
 // ReSharper disable once CheckNamespace

src/Arcus.Messaging.Abstractions.ServiceBus/MessageHandling/IAzureServiceBusMessageHandler.cs

@@ -1,8 +1,9 @@
 using System;
 using Arcus.Messaging.Abstractions.MessageHandling;
+using Arcus.Messaging.ServiceBus;
 using Azure.Messaging.ServiceBus;
 
-namespace Arcus.Messaging
+namespace Arcus.Messaging.ServiceBus
 {
     /// <summary>
     /// Represents a handler for a specific <see cref="ServiceBusReceivedMessage"/> in a <see cref="ServiceBusMessageContext"/>

src/Arcus.Messaging.Abstractions.ServiceBus/Telemetry/IServiceBusMessageCorrelationScope.cs

@@ -1,5 +1,6 @@
 using Arcus.Messaging.Abstractions.MessageHandling;
 using Arcus.Messaging.Abstractions.Telemetry;
+using Arcus.Messaging.ServiceBus;
 
 namespace Arcus.Messaging.Abstractions.ServiceBus.Telemetry
 {

src/Arcus.Messaging.Pumps.ServiceBus/Resiliency/CircuitBreakerServiceBusMessageHandler.cs

@@ -5,9 +5,10 @@
 using Arcus.Messaging.Abstractions.ServiceBus;
 using Arcus.Messaging.Abstractions.ServiceBus.MessageHandling;
 using Arcus.Messaging.Pumps.Abstractions.Resiliency;
+using Arcus.Messaging.ServiceBus;
 using Microsoft.Extensions.Logging;
 
-namespace Arcus.Messaging
+namespace Arcus.Messaging.ServiceBus
 {
     /// <summary>
     /// Represents a template for a message handler that interacts with an unstable dependency system that requires a circuit breaker to prevent overloading the system.

src/Arcus.Messaging.Pumps.ServiceBus/ServiceBusMessagePump.cs

@@ -7,6 +7,7 @@
 using Arcus.Messaging.Abstractions.ServiceBus.Telemetry;
 using Arcus.Messaging.Abstractions.Telemetry;
 using Arcus.Messaging.Pumps.ServiceBus.Configuration;
+using Arcus.Messaging.ServiceBus;
 using Azure.Messaging.ServiceBus;
 using Microsoft.Extensions.DependencyInjection;
 using Microsoft.Extensions.Hosting;