Service status contains only one effective address #10
Description
Problem
The Service object status has EffectiveAddress property that is supposed to advertise the network address the Service can be reached at. Problem is, depending on what kind of address the Service spec contains, there can be multiple resulting effective addresses that the Service will be listening on.
We actually listen on all the resolved network addresses, we just do not advertise them through status.
What we should do instead is have a list of effective address-port combination in the status.
Tactics
This will be a breaking change for Aspire, one that we could do for Aspire 10 (e.g. do a staged change by introducing new address information into status and deprecating old EffectiveAddress and EffecitvePort properties, then updating Aspire, then removing the obsolete properties).