Node `Guardian` is Banning its Own IP Address

[rotilho]

The Guardian service, is incorrectly identifying its own IP address as a source of excessive requests and subsequently banning it. This is observed through log messages similar to:
Banning node-adventurous.live.core.atto.cash/34.54.218.30. Received 1068 requests while median of voters is 104 per second
where node-adventurous.live.core.atto.cash/34.54.218.30 is the public URI and IP address of the node itself.

The Guardian service is intended to ignore self-originated requests by comparing the publicUri of an incoming message with the node's own thisNode.publicUri. The self-banning indicates a failure in this self-identification mechanism or potentially symptom of a connection issue.

Current Behavior:
The node's Guardian service logs a message indicating it is banning its own IP address due to exceeding the request rate threshold.