CLPR: ClprEndpoint Network Address Publication Is Global Config

In development, we've configured all nodes with ClprConfig of `clpr.publicizeNetworkAddresses` which determines whether or not the ClprLedgerConfiguration has values for ServiceEndpoint in the ClprEndpoint data structures, publicizing the network addresses of nodes. Since the locally generated ClprLedgerConfiguration is stored in the state, if nodes have different local configuration settings, an ISS and potentially a Catastrophic ISS can occur. This value needs to become a globally agreed upon value for the whole network. We shouldn't be able to have rogue nodes change the configuration, produce a ClprLedgerConfiguration that causes an ISS.

I could be wrong about this and maybe this policy is best set by local config and coordination by node operators. I am creating this issue to make sure we have a definite decision after deep consideration.

No file or test paths are provided. Start by tracing ClprConfig, clpr.publicizeNetworkAddresses, ClprLedgerConfiguration, and ClprEndpoint to understand how local settings enter persisted state and whether nodes can disagree. Done requires a documented decision on global agreement versus local configuration, followed by an implementation and validation that inconsistent node settings cannot produce an ISS.

Written by the indexing model from the issue text.