Fix duplicate port-zero tracker instance bootstrap

[josecelano]

Goal

Start every configured HTTP and UDP tracker instance with its own configuration, including repeated same-protocol 0.0.0.0:0 blocks.

Revised Delivery Plan

An earlier implementation attempt is archived on reference branch archive/2035-bootstrap-identity-attempt. It is not proposed for merge. Manual verification found that bootstrap identity alone cannot make per-listener UDP metrics correct: UDP server metrics currently use a global event path, and producer-side suppression can hide facts needed by UDP banning.

Reimplement #2035 after:

1. Define canonical runtime service identity #2036 defines canonical runtime service/configuration-instance identity.
2. Migrate runtime service registry metadata #2041 migrates that identity through started-service registration metadata.
3. Normalize per-instance event metrics policy #2039 normalizes event publication and listener-side metrics filtering.

Scope

• Preserve each configured HTTP/UDP instance when configured bind addresses are equal.
• Use canonical identity, not configured SocketAddr, for bootstrap correlation.
• Start each configuration entry with its matching container.
• Correlate lifecycle logs with canonical identity and bindings.
• Add regressions with repeated 0.0.0.0:0 blocks.

Out of scope

• Runtime registry metadata: Migrate runtime service registry metadata #2041.
• Event-metrics normalization: Normalize per-instance event metrics policy #2039.
• Public topology/configuration changes.

References

• Archived reference branch: josecelano/archive/2035-bootstrap-identity-attempt
• Define canonical runtime service identity #2036
• Normalize per-instance event metrics policy #2039
• Migrate runtime service registry metadata #2041
• Allow multiple integration tests at the main app level #1419