fix: use explicit address equality
Merged
RE
3mo ago+19+19+01234567890123456789-19-19-01234567890123456789
Some address comparisons can bind to an unintended equality overload when written with == or !=. Use explicit Equals calls for IPAddress and SiloAddress comparisons across networking, placement, and diagnostics.
This PR is stacked on https://github.com/dotnet/orleans/pull/10256 so the commits appear in the same order as the dissemination branch; merge the parsing PR first.