Issue Description:
The issue happens in case Bridge/Processor transition from PROVISIONING to READY takes a longer time than interval of Shard querying to Manager (30 seconds by default).

In such case the Shard notifies the Manager that the Bridge is ready [1] even though the BridgeIngress status is not checked and reconciliation process is still running.

The issue can be reproduced on slower environments (where transition from PROVISIONING to READY takes a longer time than interval of Shard querying to Manager) by deleting Bridge/Processor right after it is switched to ready state. As a result the Bridge/Processor deletion either fails or the Bridge/Processor is reset by Shard back to ready state.

Example of such issue is attached as logs.

Acceptance Criteria:

• Bridge/Processor can be properly deleted right after its state is switched to READY

Out of Scope:

Additional Information:

[1] https://github.com/5733d9e2be6485d52ffa08870cabdee0/sandbox/blob/main/shard-operator/src/main/java/com/redhat/service/smartevents/shard/operator/BridgeIngressServiceImpl.java#L75-L79