chore(remove): event-hubs pump project

docs/preview/02-Features/05-event-hubs-extensions.md

@@ -55,8 +55,6 @@ The Arcus message pump/router automatically makes sure that received Azure Event
 If you also want the sender (dependency tracking) to be linked to the request, we provide a set of easy extensions on the `EventHubProducerClient` to make this happen.
 For more information on dependency tracking, see the [Arcus Observability feature documentation on telemetry tracking](https://observability.arcus-azure.net/features/writing-different-telemetry-types/).
 
-> 🚩 By default, the EventHubs message pump is using W3C correlation, not Hierarchical, which already allows automatic dependency tracking upon sending without additional configuration. If you want to use Hierarchical, please configure the correlation format in the [message pump configuration](./02-message-handling/03-event-hubs.md).
-
 Internally, we enrich the `EventData` with the message correlation and track the entire operation as an Azure EventHubs dependency.
 The result of this operation will result in a parent-child relationship between the dependency-request.
 

docs/preview/02-Features/06-general-messaging.md

@@ -155,5 +155,4 @@ public class RateLimitService
 ⚡ Besides the `PauseProcessingMessagesAsync` method, there also exists `Stop...`/`Start...` variants so that you can control the time dynamically when the pump is allowed to run again.
 
 For more information on message pumps:
-- [Azure Service Bus message pump](./02-message-handling/01-service-bus.md)
-- [Azure EventHubs message pump](./02-message-handling/03-event-hubs.md)
+- [Azure Service Bus message pump](./02-message-handling/01-service-bus.md)