[Question] Conflict Between URIRegister and DiscoveryConfigRegister During Initial Service Registration

### Question

I encountered an issue during the initial automatic registration of a service where the URIRegister and DiscoveryConfigRegister processes conflict.

The URIRegister process creates a default discovery of type local.
The DiscoveryConfigRegister process registers the configured discovery (in my case, Zookeeper).
The execution order of these processes cannot be controlled. Sometimes, the URIRegister process executes first, resulting in the creation of a local type discovery. Occasionally, this also leads to concurrency issues, causing duplicate creation of discovery_rel data.

Currently, the only workaround is to manually create selectors and discovery configurations for each service in the Divide plugin, which avoids errors caused by automatic creation.

Could you please advise on how to avoid these conflicts or disable the URIRegister process without modifying the code?

Start by tracing the URIRegister and DiscoveryConfigRegister registration paths and compare them with the Divide plugin's manual selector and discovery configuration path. Done means identifying a supported configuration or documented way to avoid the registration conflict and duplicate discovery_rel creation.

Written by the indexing model from the issue text.