Improve logging for Cluster.Bootstrap hostname matching diagnostics

[Aaronontheweb]

Summary

Addresses #3387 by adding detailed diagnostic logging to help debug hostname/IP mismatch issues during cluster bootstrap.

Changes

1. HostMatches method - Added DEBUG logging showing:

   • Self hostname being compared
   • Target hostname from discovery
   • Target IP address (if available)
   • Direct string match result
   • Contains match result
   • Final match result

2. MatchesSelf method - Added DEBUG logging for the edge case where hostname matches but port doesn't

3. CanJoinSelf warning - Enhanced to separately display hostname and port values when self contact point is not found in discovered targets

4. AkkaManagement binding log - Now shows the advertised hostname alongside the bind address to clarify the difference

Example Logs

Before:

[INFO] Binding Akka Management (HTTP) endpoint to: 0.0.0.0:8558
[INFO] Located service members based on: [Lookup(drawtogether, management, tcp)]: [ResolvedTarget(10.1.2.138, 8558, 10.1.2.138)], filtered to [10.1.2.138:8558]
[INFO] Contact point [akka.tcp://DrawTogether@drawtogether-0.drawtogether:5055] returned [0] seed-nodes []

After (with DEBUG enabled):

[INFO] Binding Akka Management (HTTP) endpoint to: 0.0.0.0:8558, advertising as hostname: drawtogether-0.drawtogether
[DEBUG] HostMatches comparison: self hostname='drawtogether-0.drawtogether', target hostname='10.1.2.138', target address='10.1.2.138', direct match=False, contains match=False, result=False
[WARN] Self contact point [drawtogether-0.drawtogether:8558] (hostname: drawtogether-0.drawtogether, port: 8558) not found in targets [10.1.2.138:8558]

Testing

No new tests required - these are purely observability improvements that don't change any logic or require infrastructure modifications.

Fixes #3387