Introduce event publishing management for integration components and adjust Azure Service Bus customization to install the topics during provisioning

[danielmarbach]

During the introduction of the default topology, we did not account for the fact that integration events are published by default. When the required entities do not exist, the transport swallows the “entity not found” exception. However, this only happens after several retries by the Azure SDK, which can result in warning logs and, in the worst case, reduce the efficiency of the integration event publisher.

This PR addresses that issue by ensuring that all published event types are registered and carried forward into transport provisioning. Most transports are unaffected, but Azure Azure Service Bus, in the context of ServiceControl, requires these entities to exist. With this change, the transport can provision the required topics so publishing succeeds without unnecessary retries.

Provisioning behavior still respects existing configuration:

• When SkipQueueCreation is enabled, topics will not be created.
• When an instance is configured with DisableIntegrationEventPublishing = true, integration-event-related infrastructure will not be provisioned. If someone sets the flag to true during setup and later sets it to false then no infrastructure would have been provisioned, and the failure will be logged, which is expected.

In addition, this PR slightly refactors the integration event setup so it aligns better with the already componentized infrastructure.

While working on this change, I also discovered that when MessagesEditedAndRetried was introduced, the event was not added to EventsToMigrate. This is now handled automatically, reducing the risk of similar omissions in the future.