… are exposed to service consumers

Each workload will define its endpoint/s publishing default so a
mechanism is required to override the default with the options passed by
the user in the external API.

To unlock the possibility of deploying 2 different publishing strategies
for the same endpoint, the whole list of strategies needs to be
replaces, because with Merge only one strategy can exists per endpoint,
otherwise it wouldn't know how to do the merge.
Replace allows exposing the same endpoint through several different
strategies in parallel, which unlocks the possiblity of DNS based migrations without
downtime.